Service profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices

ABSTRACT

Various embodiments are disclosed for a services policy communication system and method. In some embodiments, an intermediate networking device provides a service intermediary or intermediate connection between a network and one or more communications devices; implements a service profile set for assisting control of the intermediate networking device use of a service set on the network, wherein the service profile set includes one or more service profiles, each profile being associated with either the intermediate networking device or a communications device, each profile further including a plurality of service policy settings; and monitors use of the service set based on the service profile set, in which the implementation of the first service profile set is verified.

CROSS REFERENCE TO OTHER APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 61/206,354 (Attorney Docket No. RALEP001+) entitled SERVICES POLICYCOMMUNICATION SYSTEM AND METHOD filed Jan. 28, 2009, U.S. ProvisionalPatent Application No. 61/206,944 (Attorney Docket No. RALEP002+)entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 4,2009, U.S. Provisional Application No. 61/207,393 (Attorney Docket No.RALEP003+) entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHODfiled Feb. 10, 2009, and U.S. Provisional Patent Application No. ______(Attorney Docket No. RALEP004+) entitled SERVICES POLICY COMMUNICATIONSYSTEM AND METHOD filed on Feb. 13, 2009, which are incorporated hereinby reference for all purposes.

BACKGROUND OF THE INVENTION

With the advent of mass market digital communications and contentdistribution, many access networks such as wireless networks, cablenetworks and DSL (Digital Subscriber Line) networks are pressed for usercapacity, with, for example, EVDO (Evolution-Data Optimized), HSPA (HighSpeed Packet Access), LTE (Long Term Evolution), WiMax (WorldwideInteroperability for Microwave Access), and Wi-Fi (Wireless Fidelity)wireless networks increasingly becoming user capacity constrained.Although wireless network capacity will increase with new highercapacity wireless radio access technologies, such as MIMO(Multiple-Input Multiple-Output), and with more frequency spectrum beingdeployed in the future, these capacity gains are likely to be less thanwhat is required to meet growing digital networking demand.

Similarly, although wire line access networks, such as cable and DSL,can have higher average capacity per user, wire line user serviceconsumption habits are trending toward very high bandwidth applicationsthat can quickly consume the available capacity and degrade overallnetwork service experience. Because some components of service providercosts go up with increasing bandwidth, this trend will also negativelyimpact service provider profits.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 illustrates a simplified (e.g., “flattened”) network architecturein accordance with some embodiments.

FIG. 2 illustrates another simplified (e.g., “flattened”) networkarchitecture including an MVNO (Mobile Virtual Network Operator)relationship in accordance with some embodiments.

FIG. 3 illustrates another simplified (e.g., “flattened”) networkarchitecture including two central providers in accordance with someembodiments.

FIG. 4 illustrates a network architecture including a Universal MobileTelecommunications System (UMTS) overlay configuration in accordancewith some embodiments.

FIG. 5 illustrates a network architecture including an Evolution DataOptimized (EVDO) overlay configuration in accordance with someembodiments.

FIG. 6 illustrates a network architecture including a 4G LTE and Wi-Fioverlay configuration in accordance with some embodiments.

FIG. 7 illustrates a network architecture including a WiMax and Wi-Fioverlay configuration in accordance with some embodiments.

FIG. 8 illustrates another simplified (e.g., “flattened”) networkarchitecture including multiple wireless access networks (e.g., 3G and4G Wireless Wide Area Networks (WWANs)) and multiple wire line networks(e.g., Data Over Cable Service Interface Specification (DOCSIS) andDigital Subscriber Line Access Multiplexer (DSLAM) wire line networks)in accordance with some embodiments.

FIG. 9 illustrates a hardware diagram of a device that includes aservice processor in accordance with some embodiments.

FIG. 10 illustrates another hardware diagram of a device that includes aservice processor in accordance with some embodiments.

FIG. 11 illustrates another hardware diagram of a device that includes aservice processor in accordance with some embodiments.

FIG. 12 illustrates another hardware diagram of a device that includes aservice processor in accordance with some embodiments.

FIG. 13 illustrates another hardware diagram of a device that includes aservice processor implemented in external memory of a System On Chip(SOC) in accordance with some embodiments.

FIG. 14 illustrates another hardware diagram of a device that includes aservice processor implemented in external memory of a System On Chip(SOC) in accordance with some embodiments.

FIGS. 15A through 15C illustrate hardware diagrams of a device thatinclude a service processor and a bus structure extension usingintermediate modem or networking device combinations in accordance withvarious embodiments.

FIG. 16 is a functional diagram illustrating a device based serviceprocessor and a service controller in accordance with some embodiments.

FIG. 17 is another functional diagram illustrating the device basedservice processor and the service controller in accordance with someembodiments.

FIG. 18 is another functional diagram illustrating the device basedservice processor and the service controller in which the serviceprocessor controls the policy implementation for multiple access networkmodems and technologies in accordance with some embodiments.

FIG. 19 is another functional diagram illustrating the service processorand the service controller in accordance with some embodiments.

FIG. 20 is another functional diagram illustrating the service processorand the service controller in accordance with some embodiments.

FIG. 21 is another functional diagram illustrating the service processorand the service controller in accordance with some embodiments.

FIG. 22 provides a table summarizing various service processor agents(and/or components/functions implemented in software and/or hardware) inaccordance with some embodiments.

FIG. 23 provides a table summarizing various service controller serverelements (and/or components/functions implemented in software and/orhardware) in accordance with some embodiments.

FIG. 24 is a functional diagram illustrating the service control devicelink of the service processor and the service control service link ofthe service controller in accordance with some embodiments.

FIG. 25 is a functional diagram illustrating framing structure of aservice processor communication frame and a service controllercommunication frame in accordance with some embodiments.

FIGS. 26A through 26E provide tables summarizing various serviceprocessor heartbeat functions and parameters in accordance with someembodiments.

FIGS. 27A through 27G provide tables summarizing various device basedservice policy implementation verification techniques in accordance withsome embodiments.

FIGS. 28A through 28C provide tables summarizing various techniques forprotecting the device based service policy from compromise in accordancewith some embodiments.

FIG. 29 is a functional diagram illustrating a device communicationsstack that allows for implementing verifiable traffic shaping policy,access control policy and/or service monitoring policy in accordancewith some embodiments.

FIG. 30 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 31 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 32 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 33 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 34 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 35 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 36 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 37 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments.

FIG. 38 is a functional diagram illustrating a device service processorpacket processing flow in accordance with some embodiments.

FIG. 39 is another functional diagram illustrating the device serviceprocessor packet processing flow in accordance with some embodiments.

FIG. 40 is another functional diagram illustrating the device serviceprocessor packet processing flow in accordance with some embodiments.

FIG. 41 provides a table summarizing various privacy levels for servicehistory reporting in accordance with some embodiments.

FIGS. 42A through 42F provide tables summarizing various service policycontrol commands in accordance with some embodiments.

FIGS. 43A through 43B are flow diagrams illustrating a flow diagram fora service processor authorization sequence as shown in FIG. 43A and aflow diagram for a service controller authorization sequence as shown inFIG. 43B in accordance with some embodiments.

FIGS. 44A through 44B are flow diagrams illustrating a flow diagram fora service processor activation sequence as shown in FIG. 44A and a flowdiagram for a service controller activation sequence as shown in FIG.44B in accordance with some embodiments.

FIGS. 45A through 45B are flow diagrams illustrating a flow diagram fora service processor access control sequence as shown in FIG. 45A and aflow diagram for a service controller access control sequence as shownin FIG. 45B in accordance with some embodiments.

FIG. 46 is a functional diagram illustrating open, decentralized, devicebased mobile commerce transactions in accordance with some embodiments.

FIGS. 47A through 47B are transactional diagrams illustrating open,decentralized, device based mobile commerce transactions in accordancewith some embodiments.

FIG. 48 illustrates a network architecture including a servicecontroller device control system and a service controller analysis andmanagement system in accordance with some embodiments.

FIG. 49 illustrates a network architecture for an open developerplatform for virtual service provider (VSP) partitioning in accordancewith some embodiments.

FIG. 50 illustrates a network architecture including a billing toservice controller interface for accommodating minimum changes inexisting central billing, AAA and/or other network components inaccordance with some embodiments.

FIG. 51 illustrates a network architecture for locating servicecontroller device control functions with AAA and network service usagefunctions in accordance with some embodiments.

FIG. 52 illustrates a network architecture for locating servicecontroller device control functions in the access transport network inaccordance with some embodiments.

FIG. 53 illustrates a network architecture for locating servicecontroller device control functions in the radio access network inaccordance with some embodiments.

FIG. 54 illustrates a network architecture for locating servicecontroller device control functions with AAA and network service usageincluding deep packet inspection functions in accordance with someembodiments.

FIG. 55 illustrates another network architecture for locating servicecontroller device control functions with AAA and network service usageincluding deep packet inspection functions in accordance with someembodiments.

FIG. 56 illustrates a 4G/3G/2G DPI/DPC enabled gateway in accordancewith some embodiments.

FIG. 57 illustrates a network architecture including the VSP workstationserver in communication with the 4G/3G/2G DPI/DPC gateways in accordancewith some embodiments.

FIG. 58 illustrates another 4G/3G/2G DPI/DPC enabled gateway inaccordance with some embodiments.

FIG. 59 illustrates another network architecture including the VSPworkstation server in communication with the 4G/3G/2G DPI/DPC gatewaysin accordance with some embodiments.

FIG. 60 illustrates a 4G/3G/2G DPI/DPC enabled gateway and servicecontroller device control system in accordance with some embodiments.

FIG. 61 illustrates another network architecture including the VSPworkstation server in communication with the 4G/3G/2G DPI/DPC gatewaysin accordance with some embodiments.

FIG. 62 illustrates another 4G/3G/2G DPI/DPC enabled gateway and servicecontroller device control system in accordance with some embodiments.

FIG. 63 illustrates another network architecture including the VSPworkstation server in communication with the 4G/3G/2G DPI/DPC gatewaysin accordance with some embodiments.

FIG. 64 illustrates another network architecture including a systemlocated in the manufacturing or distribution chain for the device thatprovides the device provisioning or partial provisioning, and anypre-activation required for the device to later activate on the networkin accordance with some embodiments.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

With the development and increasing proliferation of mass market digitalcommunications and content distribution, communication network capacitygains are being outpaced by growing digital networking demand. Forexample, some industry experts project average wireless device usage offour devices per subscriber, with a mixture of general purpose deviceslike smart phones and computers along with special purpose devices likemusic players, electronic readers, connected (e.g., networked) camerasand connected gaming devices. In addition, wire line user serviceconsumption habits are trending toward very high bandwidth applicationsthat can quickly consume the available capacity and degrade overallnetwork service experience if not efficiently managed. Because somecomponents of service provider costs go up with increasing bandwidth,this trend will also negatively impact service provider profits.

There is a need for a communication system and method that provides forflexible service plans and management of user network services toprovide consumer choice of more refined service plan offerings andefficient management of network capacity.

Also, it is becoming increasingly important to more deeply manage thelevel of services delivered to networked devices to provide costeffective services that match growing digital networking usage patterns.For example, access providers can move away from only billing for basicaccess and move toward billing for higher level service delivery withexample services including rich Internet access and email, applicationbased billing, content distribution, entertainment activities,information or content subscription or gaming. In addition, a growingnumber of new special purpose and general purpose networked devices arefueling demand for new service plans, for example, tailored to the newdevice usage models (e.g., a special service plan for an e-book readerdevice).

As network capabilities grow and new networked device offerings grow,access network service providers will realize increasing value inopening up their networks to allow innovation and expanded offerings fornetwork service consumers. However, opening up the networks to provideefficient third party definition of alternative service and billingmodels requires more flexible service and billing policy managementsolutions. For example, machine to machine applications such astelemetry, surveillance, shipment tracking and two way power controlsystems are example new applications that would require new offerings tomake such available to network service customers. The need to customizeservice offerings for these new applications requires more efficientmethods for defining, testing and launching new services with morerefined control of service functions and service costs. In someembodiments, this means billing for different types of service elements,such as total traffic, content downloads, application usage, informationor content subscription services, people or asset tracking services,real time machine to machine information or electronic commercetransactions.

In some embodiments, network user capacity is increased and user servicecosts are reduced by managing and billing for service consumption in amore refined manner (e.g., to satisfy network neutrality requirements).By managing service consumption in a user friendly manner, the overallservice capacity required to satisfy the user device needs can betailored more closely to the needs of a given user thereby reducing userservice costs and increasing service provider profits. For example,managing service usage while maintaining user satisfaction includesservice usage policy implementation and policy management to identify,manage and bill for service usage categories, such as total trafficconsumption, content downloads, application usage, information orcontent subscription services, electronic commerce transactions, peopleor asset tracking services or machine to machine networking services. Asdescribed herein, service activity is used to refer to any service usageor traffic usage that can be associated with, for example, anapplication; a network communication end point, such as an address,uniform resource locator (URL) or other identifier with which the deviceis communicating; a traffic content type; a transaction where content orother material, information or goods are transacted, purchased,reserved, ordered or exchanged; a download, upload or file transfer;email, text, SMS, IMS or other messaging activity or usage; VOIPservices; video services; a device usage event that generates a billingevent; service usage associated with a bill by account activity (alsoreferred to as billing by account) as described herein; device location;device service usage patterns, device user interface (UI) discoverypatterns, content usage patterns or other characterizations of deviceusage; or other categories of user or device activity that can beidentified, monitored, recorded, reported, controlled or processed inaccordance with a set of verifiable service control policies. As will beapparent to one of ordinary skill in the art in view of the embodimentsdescribed herein, some embodiments identify various service activitiesfor the purpose of decomposing overall service usage into finersub-categories of activities that can be verifiably monitored,categorized, cataloged, reported, controlled, monetized and used for enduser notification in a manner that results in superior optimization ofthe service capabilities for various levels of service cost or forvarious types of devices or groups. In some embodiments, it will beapparent to one of ordinary skill in the art that the terms serviceactivity or service usage are associated with categorizing and possiblymonitoring or controlling data traffic, application usage, communicationwith certain network end points, or transactions, and it will also beapparent that in some embodiments the term service activity is intendedto include one or more of the broader aspects listed above. Theshortened term service usage can be used interchangeably with serviceactivity, but neither term is intended in general to exclude any aspectof the other. In some cases, where the terms service usage or serviceactivity are used, more specific descriptors such as traffic usage,application usage, website usage, and other service usage examples arealso used to provide more specific examples or focus in on a particularelement of the more encompassing terms.

In some embodiments, employing this level of service categorization andcontrol is accomplished in a manner that satisfies user preferences. Insome embodiments, employing this level of service categorization andcontrol is accomplished in a manner that also satisfies government rulesor regulations regarding open access, for example, network neutralityrequirements. In some embodiments, service management solutions thatalso collect and/or report user or device service usage or serviceactivity behavior to determine how best to meet the user's simultaneousdesires for service quality and lower service costs are disclosed. Forexample, such monitoring and reporting are accomplished in a manner thatincludes approval by the user and in a manner that also protects theprivacy of user information and service usage behavior or serviceactivity history.

In some embodiments, a system and method is disclosed for increasingnetwork user capacity for wireless networks in the face of increasingservice demand per user by providing for a greater number of basestations, also sometimes referred to as access points, base terminals,terminal nodes or other well known acronyms, to be more easily and/ormore cost effectively deployed. For example, to simplify the process ofdeploying base stations, the installation complexity and the networkinfrastructure required for the base station to obtain backhaul serviceto the various networks that users desire to connect with are reduced.

In some embodiments, dense base station deployments are simplified byreducing the requirement to aggregate or concentrate the base stationtraffic through a specific dedicated core network infrastructure, sothat the base stations connect to the desired user networks through amore diverse set of local loop, back bone and core routing options. Thisapproach also reduces network infrastructure equipment, installation andmaintenance costs. In some embodiments, this is accomplished bydistributing the network traffic policy implementation and control awayfrom the core network by providing for more control for service policyimplementation and management on the end user device and, in someembodiments, in the end user device with respect to certain servicepolicies and the network (e.g., control plane servers) with respect toother service policies. For example, this approach facilitatesconnecting the base stations directly to the local loop Internet with aminimum of specific dedicated networking infrastructure.

In some embodiments, service and transaction billing event capture andlogging are distributed to the device. For example, providing serviceand transaction billing event capture and logging at the device providesa greater capability to monitor, classify and control deeper aspects ofservice usage or service activity at the device as compared to therelatively less capability for the same in the network infrastructure(e.g., for certain traffic flows, such as encrypted traffic flows).Furthermore, billing at the device provides for very specialized withmany different billing and service plans for different device andservice usage or service activity scenario combinations without theproblem of attempting to propagate and manage many different deep packetinspection (DPI) and traffic shaping profiles in the networkingequipment infrastructure. For example, service billing at the device canprovide for more sophisticated, more specialized and more scalablebilling and service plans.

Another form of billing that needs improvement is electronic commercetransaction billing with device assisted central billing. Today, mostcentral billing and content distribution models require eithercentralized content distribution maintained by the central serviceprovider or central billing authority, or a centralized ecommercewebsite or portal traffic aggregation system controlled by the centralservice provider or central billing provider, or both. In such systems,content and transaction providers such as media providers, applicationdevelopers, entertainment providers, transaction website providers andothers must adapt their mainstream electronic offering and commercesystems, such as shopping experience websites, to fit within the variousproprietary customized infrastructure and content storage solutions forecommerce markets, such as BREW® (Binary Runtime Environment forWireless from Qualcomm® Inc.), Symbian OS (from Symbian Software Ltd)and Apple iPhone 3G App Store (from Apple Inc.). This approach requiresa large amount of unnecessary custom interface development and stiflesopen market creativity for HTTP, WAP or portal/widget based shoppingdestinations and experiences. As disclosed below, a superior approachincludes device based transaction billing for an open ecosystem in whicha central billing provider provides users and ecommerce transactionproviders with a central billing solution and experience that does notrequire extensive custom development or ecommerce infrastructureinterfacing.

In some embodiments, products that incorporate device assisted servicepolicy implementation, network services and service profiles (e.g., aservice profile includes a set of one or more service policy settingsfor the device for a service on the network) are disclosed, as describedbelow. For example, aspects of the service policy (e.g., a set ofpolicies/policy settings for the device for network services, typicallyreferring to lower level settings, such as access control settings,traffic control settings, billing system settings, user notificationsettings, user privacy settings, user preference settings,authentication settings and admission control settings) that are movedout of the core network and into the end user device include, forexample, certain lower level service policy implementations, serviceusage or service activity monitoring and reporting including, forexample, privacy filtering, customer resource management monitoring andreporting including, for example, privacy filtering, adaptive servicepolicy control, service network access control services, service networkauthentication services, service network admission control services,service billing, transaction billing, simplified service activation andsign up, user service usage or service activity notification and servicepreference feedback and other service capabilities.

As discussed below, product designs that move certain aspects of one ormore of these service profile or service policy implementation elementsinto the device provide several advantageous solutions to the needsdescribed above. For example, benefits of certain embodiments includethe ability to manage or bill for a richer and more varied set ofnetwork services, better manage overall network capacity, better manageend user access costs, simplify user or new device service activation,simplify development and deployment of new devices with new serviceplans (e.g., service profile and billing/costs information associatedwith that service profile), equip central service providers with moreeffective open access networks for new third party solutions, simplifythe equipment and processes necessary to deploy wireless base stationsand simplify the core networking equipment required to deploy certainaccess networks.

As discussed below, there are two network types that are discussed: acentral provider network and a service provider network. The centralprovider network generally refers to the access network required toconnect the device to other networks. The central provider networkgenerally includes the physical layer, the Media Access Control (MAC)and the various networking functions that can be implemented to performauthentication, authorization and access control, and to route trafficto a network that connects to the control plane servers, as discussedbelow. The service provider network generally refers to the network thatincludes the control plane servers. In some embodiments, a centralprovider network and a service provider network are the same, and insome embodiments, they are different. In some embodiments, the owner ormanager of the central provider network and the owner or manager of theservice provider network are the same, and in some embodiments, they aredifferent.

In some embodiments, control of the device service policies isaccomplished with a set of service control plane servers that reside inthe access network or any network that can be reached by the device.This server based control plane architecture provides for a highlyefficient means of enabling third party control of services and billing,such as for central carrier open development programs or Mobile VirtualNetwork Operator (MVNO) relationships. As device processing and memorycapacity expands, moving to this distributed service policy processingarchitecture also becomes more efficient and economical. In someembodiments, several aspects of user privacy and desired networkneutrality are provided by enabling user control of certain aspects ofdevice based service usage or service activity reporting, trafficreporting, service policy control and customer resource management (CRM)reporting.

In many access networks, such as wireless access networks, bandwidthcapacity is a valuable resource in the face of the increasing popularityof devices, applications and content types that consume more bandwidth.To maintain reasonable service profit margins, a typical present serviceprovider practice is to charge enough per user for access to makeservice plans profitable for the higher bandwidth users. However, thisis not an optimal situation for users who desire to pay less for lowerbandwidth service usage or service activity scenarios.

Accordingly, in some embodiments, a range of service plan pricing can beenabled that also maintains service profitability for the serviceprovider, for example, by providing a more refined set of management andcontrol capabilities for service profiles. For example, this approachgenerally leads to service management or traffic shaping where certainaspects of a service are controlled down based on service policies tolower levels of quality of service. Generally, there are three problemsthat arise when these techniques are implemented. The first problem ismaintaining user privacy preferences in the reporting of service usageor service activity required to set, manage or verify service policyimplementation. This problem is solved in a variety of ways by theembodiments described below with a combination of user notification,preference feedback and approval for the level of traffic informationthe user is comfortable or approves and the ability to filter serviceusage or service activity, in some embodiments, specifically trafficusage or CRM reports so that only the level of information the userprefers to share is communicated. The second problem is satisfyingnetwork neutrality requirements in the way that traffic is shaped orservices are managed. This problem is solved in a variety of ways asdescribed in the embodiments described below by empowering the user tomake the choices on how service usage, service activity, traffic usageor CRM data is managed down to control costs, including embodiments onuser notification and service policy preference feedback. By allowingthe user to decide how they want to spend and manage their serviceallowance or resources, a more neutral or completely neutral approach tonetwork usage can be maintained by the service provider. The thirdproblem is to help the user have an acceptable and enjoyable serviceexperience for the lower cost plans that will result in much wider scaleadoption of connected devices and applications but are more constrainedon service activity usage or options or bandwidth or traffic usage. Aslower cost service plans are offered, including plans where the basicconnection service may be free, these service plans will require serviceprovider cost controls to maintain profitability or preserve networkcapacity that result in lower limits on service usage or serviceactivity. These lower service usage or service activity limit plans willresult in more users who are likely run over service usage limits andeither experience service shutdown or service cost overages unless theyare provided with more capable means for assistance on how to use andcontrol usage for the lower cost services. This problem is solved in avariety of ways with a rich collection of embodiments on usernotification, service usage and cost projection, user notificationpolicy feedback, user service policy preference feedback, and adaptivetraffic shaping or service policy implementation. As described herein,some embodiments allow a wide range of flexible and verifiable serviceplan and service profile implementations ranging from examples such asfree ambient services that are perhaps sponsored by transaction revenuesand/or bill by account sponsored service partner revenues, tointermediately priced plans for basic access services for mass marketuser devices or machine to machine communication devices, to moreexpensive plans with very high levels of service usage or serviceactivity limits or no limits at all. Several bill by account embodimentsalso provide for the cataloging of service usage that is not a directbenefit to end users but is needed for basic maintenance of the devicecontrol channels and access network connection, so that the maintenancetraffic service cost can be removed from the user billing or billed tonon-user accounts used to track or account for such service costs. Theseembodiments and others result in a service usage or service activitycontrol capability that provides more attractive device and servicealternatives to end users while maintaining profitability for serviceproviders and their partners.

In some embodiments, the above described various embodiments for devicebased service policy and/or service profile communications control areimplemented using network based service control, for example, forsatisfying various network neutrality and/or privacy requirements, basedon indication(s) received from the device (e.g., user input providedusing the device UI using the service processor) and network basedservice control (e.g., using a DPI service monitor or DPC policyimplementation and/or other network elements).

In some embodiments, a virtual network overlay includes a device serviceprocessor, a network service controller and a control planecommunication link to manage various aspects of device based networkservice policy implementation. In some embodiments, the virtual networkoverlay networking solution is applied to an existing hierarchicalnetwork (e.g., for wireless services), and in some embodiments, isapplied to simplify or flatten the network architecture as will befurther described below. In some embodiments, the large majority of thecomplex data path network processing required to implement the richerservice management objectives of existing hierarchical networks (e.g.,for wireless services) are moved into the device, leaving less data pathprocessing required in the edge network and in some cases even less inthe core network. Because the control plane traffic between the servicecontrol servers and the device agents that implement service policiescan be several orders of magnitude slower than the data plane traffic,service control server network placement and back-haul infrastructure ismuch less performance sensitive than the data plane network. In someembodiments, as described further below, this architecture can beoverlaid onto all the important existing access network architecturesused today. In some embodiments, this architecture can be employed togreatly simplify core access network routing and data plane trafficforwarding and management. For example, in the case of wirelessnetworks, the incorporation of device assisted service policyimplementation architectures can result in base stations that directlyconnect to the Internet local loop and the data traffic does not need tobe concentrated into a dedicated core network. This results, forexample, in a large reduction in backhaul cost, core network cost andmaintenance cost. These cost savings can be re-deployed to purchase andinstall more base stations with smaller cells, which results in higherdata capacity for the access network leading to better user experience,more useful applications and lower service costs. This flattenednetworking architecture also results in latency reduction as fewerroutes are needed to move traffic through the Internet. In someembodiments, the present invention provides the necessary teaching toenable this powerful transformation of centralized network servicearchitectures to a more distributed device based service architectures.

Device based billing can be compromised, hacked and/or spoofed in manydifferent ways. Merely determining that billing reports are beingreceived from the device, that the device agent software is present andproperly configured (e.g., the billing agent is present and properlyconfigured) is insufficient and easily spoofed (e.g., by spoofing theagent itself, providing spoofed billing reports using a spoofed billingagent or providing spoofed agent configurations). Accordingly, in someembodiments, verifiable device assisted and/or network based servicepolicy implementation is provided. For example, verifiable service usageand/or service usage billing can be provided as described herein withrespect to various embodiments.

While much of the below discussion and embodiments described below focuson paid service networks, those of ordinary skill in the art willappreciate that many of the embodiments also apply to other networks,such as enterprise networks. For example, the same device assistednetwork services that create access control services, ambient activationservices and other service profiles can be used by corporate IT managersto create a controlled cost service policy network for corporate mobiledevices. As another example, embodiments described below for providingend user service control can also allow a service provider to offerparental controls by providing parents with access to a website with aweb page that controls the policy settings for the access controlnetworking service for a child's device.

Network Architecture for Device Assisted/Based Service Control

FIG. 1 illustrates a simplified (e.g., “flattened”) network architecturein accordance with some embodiments. As shown, this provides for asimplified service infrastructure that exemplifies a simplified and“flattened” network architecture in accordance with some embodimentsthat is advantageous for wireless network architectures. This alsoreduces the need for complex data path protocol interaction between thebase station and network infrastructure. For example, in contrast to acomplex edge and core network infrastructure connecting base stations tothe central service provider network, as shown the base stations 125 areconnected directly to the Internet 120 via firewalls 124 (in someembodiments, the base stations 125 include the firewall functionality124). Accordingly, in some embodiments, a central provider network is nolonger required to route, forward, inspect or manipulate data planetraffic, because data plane traffic policy implementation is conductedin the device 100 by the service processor 115. However, it is still anoption, in some embodiments, to bring data plane traffic in from thebase stations 125 to a central provider network using either open orsecure Internet routing if desired. Base station control planecommunication for access network AAA (Authentication, Authorization, andAccounting) server 121, DNS/DHCP (Domain Name System/Dynamic HostConfiguration Protocol) server 126, mobile wireless center 132(sometimes referenced to in part as a home location register (HLR) orother acronym) or other necessary functions are accomplished, forexample, with a secure IP tunnel or TCP connection between the centralprovider network and the base stations. The base station 125 is used torefer to multiple base station embodiments where the base station itselfis directly connected to the RAN, or where the base station connects toa base station controller or base station aggregator function that inturn connects to the RAN, and all such configurations are collectivelyreferred to herein as base station 125 in FIG. 1 and most figures thatfollow that reference base station 125 as described below.

As shown, the central provider access network is both 3G and 4G capable,the devices 100 can be either 3G, 4G or multi-mode 3G and 4G. Those ofordinary skill in the art will also appreciate that in the more generalcase, the network could be 2G, 3G and 4G capable, or the device could be2G, 3G and 4G capable with all or a subset of Global System for Mobile(GSM), General Packet Radio Service (GPRS), Code Division MultipleAccess (CDMA) 1X, High Speed Packet Access (HSPA), Evolution DataOptimized (EVDO), Long Term Evolution (LTE) and WiMax modem capability.If the devices are single mode, then the 3G devices 100 will beactivated with a service profile applied to service processor 115 thatis consistent with the 3G network capacity and speed, and the 4G deviceswill be activated with service profiles applied to service processor 115that are consistent with 4G network capacity and speed. In both cases,the same service controller 122 manages services for both sets ofdevices in accordance with some embodiments. If the devices aremultimode, then the service processor 115 can be activated with a dualmode service profile capability in which the service profile for 3Goffers a similar rich set of services as the service profile for 4G butwith, for example, scaled back bandwidth. For example, this approach isallows central providers to offer a richer set of service offerings with3G and then migrate the same set of service offerings to 4G but withhigher performance. In particular, this approach allows 3G to 4G richservice migration to occur, for example, with the only change being theincreased bandwidth settings in the service profiles that will beavailable in 4G at the same cost as 3G with lower service profilebandwidth settings.

In some embodiments, if the devices are multimode, a network selectionpolicy implementation within service processor 115 is provided, or insome embodiments, a network selection policy is driven by policydecisions made in service controller 122 based on service availabilityreports received from service processor 115. The network selectionpolicy allows the selection of the network that corresponds to the mostdesirable service profile to meet the user's service preferences. Forexample, if the user specifies, within the framework of the servicenotification and user preference feedback embodiments described below,that maximum performance is the most important factor in selecting whichaccess network to connect to, then the best profile is likely to be the4G network as 4G is typically faster, except perhaps, for example, ifthe device 100 is closer to the 3G base station so that there is a muchstronger signal or if the 4G network is much more heavily loaded thanthe 3G network. On the other hand, if the user preference set specifiescost as the most important factor, then depending on the centralprovider service costs the 3G network may prove to be the most desirableservice profile. This is a simple example and many other selectioncriteria are possible in the network selection embodiment as discussedfurther below.

Network Based Service Usage Monitoring for Verification and OtherPurposes

In some embodiments, if the base station data plane traffic istransmitted via the Internet 120 as discussed above, then IPDRs(Internet Protocol Detail Records, also sometimes and interchangeablyreferred to herein as Charging Data Records or CDRs, which as usedherein refer to any network measure of service usage or service activityfor voice and/or data traffic (e.g., IPDRs can include a time stamp, adevice ID, and various levels of network measures of service usage forthe device associated with that device ID, such as perhaps total trafficusage, network destination, time of day or device location)) aregenerated by and collected from the access network equipment. Dependingon the specific network configuration, as discussed herein, for a WWANnetwork the IPDRs can be generated by one or more of the following: basestation 125, RAN or transport gateways and AAA 121. In some accessnetwork embodiments, the IPDRs are transmitted to equipment functionsthat aggregated the IPDRs for the purpose of service billing and otherfunctions. Aggregation can occur in the AAA, the transport gateways orother functions including the billing system 123. As discussed below, itis often the case that the IPDRs is assumed to be obtained from the AAAserver 121 and/or a service usage data store 118 (e.g., a real-timeservice usage collection stored in a database or a delayed feed serviceusage collection stored in a database), or some other network function.However, this does not imply that the IPDRs may not be obtained from avariety of other network functions, and in some embodiments, the IPDRsare obtained from other network functions as disclosed herein. In someembodiments, existing IPDR sources are utilized to obtain network basedservice usage measures for multiple purposes including but not limitedto service policy or profile implementation verification, triggeringservice verification error responds actions, and service notificationsynchronization. Certain types of IPDRs can be based on, or based inpart on, what are sometimes referred to as CDRs (Charging Data Records,which can track charges for voice and data usage) or modifications ofCDRs. Although the capability to monitor, categorize, catalog, reportand control service usage or service activity is in general higher onthe device than it is in the network, and, as described herein, devicebased service monitoring or control assistance is in some ways desirableas compared to network based implementations, as described herein manyembodiments take advantage of network based service monitoring orcontrol to augment device assisted service monitoring or control andvice versa. For example, even though many embodiments work very wellwith minimal IPDR service usage or service activity information that isalready available in a network, deeper levels of IPDR packet inspectioninformation in general enable deeper levels of service monitoring orservice control verification, which can be desirable in someembodiments. As another example, deeper levels of network capability tocontrol service usage or service activity can provide for moresophisticated error handling in some embodiments, for example, providingfor more options of the Switched Port Analyzer (SPAN) and networkquarantine embodiments as described herein. As another example, in someembodiments it is advantageous to take advantage of network basedservice monitoring or control for those service aspects the network iscapable of supporting, while using device assisted service monitoring orcontrol for the service aspects advantageously implemented on thedevice.

In some embodiments, where base station data plane traffic is backhauledand concentrated in a central provider core network 110, then the IPDRscan originate in the base stations or a router or gateway in the centralprovider network 110, and the IPDRs are collected at the AAA server 121and stored in the service usage data store 118. In some embodiments, thecentral billing system 123 collects the IPDRs from the AAA server 121for service billing accounting purposes. In some embodiments, a centralbilling system 123 collects the IPDRs directly from the initial IPDRsource or some other aggregator. In some embodiments, outside partnerslike MVNOs gain access to the IPDRs from the central billing system 123.As discussed below, it is assumed that the IPDRs are obtained from theAAA server 121, and it is understood that the source of the IPDRs isinterchangeable in the embodiments.

In some embodiments, the IPDR information is used by the serviceprocessor 115, the service controller 122 and/or other network apparatusor device apparatus to implement service control verification isprovided as described below. In some embodiments, an IPDR feed (e.g.,also referred to as a charging data record (CDR)) flows between networkelements. For example, an IPDR feed can flow from the RAN gateway 410(e.g., SGSN 410, BSC packet control 510 or RNC 512) and the transportgateway 420 (e.g., GGSN or PDSN). In other embodiments, the IPDRsoriginate and flow from the base station 125 or some othercomponent/element in the network. In some embodiments, one or more ofthese IPDR feeds is transmitted to an IPDR aggregation function (e.g.,also referred to as a charging gateway). For example, this aggregationfunction can be located in the AAA 121, in the mobile wireless center132 (and/or in the home location register (HLR) or other similarfunction referred to by other common industry names), in the transportgateway 420, or in some other network element. This aggregation functioncollects the IPDR feeds into a database with an entry for each device100. In some embodiments, an intermediate aggregation function isprovided that feeds a higher level aggregation function, for example,the transport gateway 420 can receive IPDR feeds from the RAN gateway410 or the base station 125 before sending them to another aggregationfunction. At some point in time (e.g., at the end of a specified timeperiod, at the end of a device network connection session and/or at aspecified time of day), the IPDR aggregation function sends summaryinformation or detailed information of the IPDRs for a given device orgroup of devices to the billing system for billing and/orreconciliation. In some embodiments, in which the IPDR aggregation feedto the billing system is frequent enough for one or more of the IPDRinformation purposes described herein, the IPDR feed for the servicecontroller 122 is derived from the aggregated feed, either by having thebilling system 123 transmit it to the service controller 122, or bycopying it from the IPDR aggregation function.

In some embodiments, the IPDR feed is obtained from the network functionthat is generating or aggregating the IPDR feed as described herein. Insome embodiments, the IPDR feed is copied from the aggregation functionin a manner that does not interrupt the operation of the network. Forexample, a switch based port analysis function can be used to copy thetraffic to a traffic analysis or server element that filters out theIPDR traffic and records it to a data base that is then either pushed tothe service controller 122 (or any other network element that uses IPDRinformation as described herein), or is queried by the servicecontroller 122 (or any other function that uses the IPDR information asdescribed herein). In some embodiments, if the aggregated IPDRinformation transmitted to the billing system is delayed from real-timetraffic usage events by an amount of time that is, for example, too longfor desired operation, or for any other reason that makes it lessdesirable to obtain the IPDR information from the same aggregated feedused for the billing system 123, the IPDR information can be collectedfrom one or more of the sources discussed above including, for example,from another aggregation point (e.g., the feed to the charging gateway,AAA server and/or mobile wireless center/HLR), one or more of thegateways 410, 420, 508, 512, 520, 608, 612, 620, 708, 712, 720 the basestation 125 and/or another network element. In some embodiments, theIPDR feeds from these or other network functions are copied to adatabase as described above, which is either pushed or queried to getthe information to the service controller 122 or other network elementsthat request the IPDR information.

In some embodiments, the service processor 115 includes variouscomponents, such as device agents, that perform service policyimplementation or management functions. In some embodiments, thesefunctions include service policy or implementation verification, servicepolicy implementation tamper prevention, service allowance or denial,application access control, traffic control, network access controlservices, various network authentication services, service control planecommunication, device heartbeat services, service billing, transactionbilling, simplified activation services and/or other serviceimplementations or service policy implementations. It will be apparentto those of ordinary skill in the art that the division in functionalitybetween one device agent and another is a design choice, that thefunctional lines can be re-drawn in any technically feasible way thatthe product designers see fit, and that the placing divisions on thenaming and functional breakouts for device agents aids in understanding,although in more complex embodiments, for example, it can make sense tothe product designer to break out device agent functionalityspecifications in some other manner in order to manage developmentspecification and testing complexity and workflow.

In some embodiments, network control of the service policy settings andservices as discussed above is accomplished with the service controller122 which in various embodiments includes one or more server functions.As with the service processor 115 agent naming and functional break out,it is understood that service controller 122 server naming andfunctional breakout is also a design choice and is provided mainly toaid in the discussion. It will be apparent to those of ordinary skill inthe art that the server names and functional breakouts do not imply thateach name is an individual server, and, for example, a single namedfunction in the various embodiments can be implemented on multipleservers, or multiple named functions in the various embodiments can beimplemented on a single server.

As shown, there are multiple open content transaction partner sites 134(e.g., open content transaction servers), which represent the websitesor experience portals offered by content partners or ecommercetransaction partners of the service provider. For example, transactionservers 134 can provide an electronic commerce offering and transactionplatform to the device. In some embodiments, the central provider hasownership and management of the service controller 122, so the centralprovider and the service provider are the same, but as discussed belowthe service provider that uses the service controller 122 to manage thedevice services by way of service processor 115 is not always the sameas the central provider who provides the access network services.

In some embodiments, further distribution of central provider accessnetworking functions such as access network AAA server 121, DNS/DHCPserver 126, and other functions are provided in the base stations 125.In some embodiments, network based device service suspend/resume controlare also provided in the base stations 125 (or in some embodiments, forhierarchical or overlay networks, this function is provided by one ormore of the following: RAN gateways, transport gateways, AAA 121 or someother network function). As shown, the following are connected (e.g., innetwork communication with) the central provider network 110: centralprovider billing system 123, dedicated leased lines 128 (e.g., for otherservices/providers), central provider service controller 122, a contentmanagement (e.g., content switching, content billing, and contentcatching) system 130, central provider DNS/DHCP server 126, accessnetwork AAA server 121, service usage data store 118 and centralprovider mobile wireless center 132. These embodiments may beadvantageous particularly for flat networks as that shown in FIG. 1 thatare provided by the present invention.

In some embodiments, the base stations 125 implement a firewall functionvia firewall 124 and are placed directly onto the local loop Internetfor backhaul. Voice traffic transport is provided with a secure protocolwith Voice Over IP (VOIP) framing running over a secure IP session, forexample, Virtual Private Network (VPN), IP Security (IPSEC) or anothersecure tunneling protocol. In some embodiments, the VOIP channel employsanother layer of application level security on the aggregated VOIPtraffic trunk before it is placed on the secure IP transport layer. Basestation control traffic and other central provider traffic can beprovided in a number of ways with secure transport protocols runningover Transmission Control Protocol (TCP), Internet Protocol (IP) or UserDatagram Protocol (UDP), although TCP provides a more reliable deliverychannel for control traffic that is not as sensitive to delay or jitter.One example embodiment for the control channel is a control linkbuffering, framing, encryption and secure transport protocol similar tothat described below for the service control link between a device andthe network. In some embodiments, a service control heartbeat functionis provided to the base stations 125 similar to that implemented betweenthe service controller 122 and the service processor 115 as describedbelow. If the need to maintain a bandwidth efficient control planechannel between the base stations and the central provider base stationcontrol network is not as critical as it is in the case of accessnetwork connection to the device, then there are many other approachesfor implementing a secure control channel over the Internet including,for example, one or more of various packet encryption protocols runningat or just below the application layer, running TCP Transport LayerSecurity (TLS), and running IP level security or secure tunnels.

In some embodiments, the device based services control plane trafficchannel between the service processor 115 and the service controller 122is implemented over the same control plane channel used for the flatbase station control architecture, or in some embodiments, over theInternet. As discussed below, it is assumed that the device basesservices control plane channel for service processor 115 to servicecontroller 122 communications is established through the Internet 120 orthrough the access network using IP protocols as this is the moregeneral case and applies to overlay network applications for variousembodiments as well as applications where various embodiments are usedto enable flattened access networks.

In some embodiments, by enabling the device to verifiably implement arich set of service features as described herein, and by enabling thebase station 125 to connect directly to the Internet 120 with a localfirewall for device data traffic, tunnel the voice to a voice networkwith VOIP and secure Internet protocols, and control the base station125 over a secure control plane channel using base station controlservers located in a central provider network, base stations 125 can bemore efficiently provisioned and installed, because, for example, thebase station 125 can accommodate a greater variety of local loopbackhaul options. In such embodiments, it is advantageous to performcertain basic network functions in the base station 125 rather than thecentral provider network.

In some embodiments, a basic device suspend/resume function for allowingor disallowing the device Internet access is provided by the basestations 125 (or in some embodiments, for hierarchical or overlaynetworks in some embodiments this function is provided by one or more ofthe following: RAN gateways, transport gateways, AAA 121 or some othernetwork function). This functionality, as will be discussed below, isimportant for certain embodiments involving taking action to resolve,for example, service policy verification errors. In some embodiments,this function is performed at the base station (e.g., base stations 125)thereby eliminating the need for a more complex networking equipmenthierarchy and traffic concentration required to perform thesuspend/resume function deeper in the network. Access network basestations control media access and are therefore designed with awarenessof which device identification number a given traffic packet, group ofpackets, packet flow, voice connection or other traffic flow originatesfrom and terminates to. In some embodiments, the suspend/resume functionis implemented in the base station 125 by placing an access controlfunction in the traffic path of each device traffic flow. The suspendresume function can be used by various network elements, and in thecontext of the present embodiment can be used by the service controller122 (e.g., in some embodiments, access control integrity server 1654(FIG. 16) of service controller 122 or other service controllerelements) to suspend and resume device service based on the assessmentof the service policy implementation verification status as describedbelow.

In some embodiments, at least a basic traffic monitoring or servicemonitoring function is performed at the base station (e.g., basestations 125) similar to the service history records or IPDRs collecteddeeper in the network in more conventional hierarchical access networkinfrastructure architectures. For example, the service or trafficmonitoring history records are advantageous for tracking device networkservice usage or service activity behavior and for certain verificationmethods for device based service policy implementation or higher devicebased services as discussed below. In some embodiments, a trafficmonitoring function is provided in the base station 125 in which thetraffic for each device is at least counted for total traffic usage andrecorded. In some embodiments, traffic inspection beyond simply countingtotal traffic usage is provided. For example, the base station trafficmonitor can record and report IP addresses or include a DNS lookupfunction to report IP addresses or IP addresses and associated UniformResource Locators (URLs). Another example allows the base station 125 toattach location data to the IPDR to provide device location data in therecords. In some embodiments, traffic inspection includes recordingdeeper levels of traffic or service monitoring.

In some embodiments, device traffic associated with service verificationconditions indicating service usage is out of policy or profile limitsor allowances is routed to a quarantine network rather than or as aninitial alternative to a suspending service. For example, the advantagesfor this approach and a more detailed description of the quarantinenetwork are discussed below. In some embodiments, the quarantine networkcapability is provided for in which rather than simply suspending devicetraffic completely from the network as described above, the base station125 includes a firewall function (e.g., firewall 124) that is capable ofpassing device access traffic with the quarantine network destinationsand blocking device access to all other destinations. In someembodiments, when it is discovered that service verification conditionsindicate that service usage is out of policy or profile limits orallowances, then one or more of the following actions are taken: theuser is notified of the overage condition, the user is required toacknowledge the overage condition, the user account is billed for theoverage condition, and the device is flagged for further analysis by anetwork device analysis function or a network manager.

In some embodiments, network complexity is reduced using the devicewithout moving completely to a flat base station network as describedabove. Device participation in the core network services implementationprovides for numerous measures for simplifying or improving networkarchitecture, functionality or performance. For example, two approachesare discussed below ranging from a simple overlay of the serviceprocessor 115 onto devices and the service controller 122 in aconventional hierarchical access network as illustrated in FIGS. 4through 7, to a completely flat network as illustrated in FIGS. 1through 3 and 8. Those of ordinary skill in the art will appreciate thatthe disclosed embodiments provided herein can be combined with the aboveembodiments and other embodiments involving flat network base stationsto provide several advantages including, for example, richer servicecapability, less access network complexity, lower access networkexpenses, more flexible base station deployments, or less complex orless expensive base station back haul provisioning and service costs.

In most of the discussion that follows, the network based servicehistory records and the network based suspend-resume functionality usedin certain embodiments involving service implementation verification areassumed to be derived from the device service history 1618 (as shown inFIG. 16) central provider network element and the AAA server 121 centralprovider network element, and in some embodiments, working inconjunction with other central provider network elements. It isunderstood that these functions provided by the network can berearranged to be provided by other networking equipment, including thebase station as discussed above. It is also understood that the networkbased device traffic monitoring, recording and reporting to the deviceservice history 1618 element can be accomplished at the base stations.Furthermore, it is understood that while the AAA server 121 is assumedto provide the suspend/resume functionality, quarantine network routingor limited network access called for in some embodiments, the AAA server121 can be a management device in which the actual implementation of thetraffic suspend/resume, firewall, routing, re-direction forwarding ortraffic limiting mechanisms discussed in certain embodiments can beimplemented in the base stations as discussed above or in anothernetwork element.

In some embodiments, an activation server 160 (or other activationsequencing apparatus) provides for provisioning, as described below, ofthe devices 100 and/or network elements in the central provider networkso that, for example, the device credentials can be recognized foractivation and/or service by the network. In some embodiments, theactivation server 160 provides activation functions, as described below,so that, for example, the devices can be recognized by the network, gainaccess to the network, be provided with a service profile, be associatedwith a service account and/or be associated with a service plan. Asshown in FIG. 1, the activation server 160 is connected to the centralprovider core network 110. In this configuration, the activation server160 acts as, an over the network or over the air, activation function.In some embodiments, the activation server 160, or variations of theactivation server 160 as described below, is connected to apparatus inthe manufacturing or distribution channel, or over the Internet 120, oras part of the service controller 122 to service provisioning oractivation functions. In some embodiments, the activation server 160 isconnected to the central provider core network 110. In some embodiments,the activation server 160 is connected to other network extensions suchas an MVNO network or the Internet 120 if, for example, the routers inthe service gateways or base stations have the capability to directtraffic from devices that are not fully activated or provisioned to anInternet destination, or if the service processor 115 is used for suchdirection. In some embodiments, the activation server 160 is included inthe service controller 122.

FIG. 2 illustrates another simplified (e.g., “flattened”) networkarchitecture including an MVNO (Mobile Virtual Network Operator)relationship in accordance with some embodiments. As shown, an open MVNOconfiguration is provided in a simplified network as similarly describedabove with respect to FIG. 1. In some embodiments, the service provider(e.g., service owner) is defined by the entity that maintains and/ormanages the service controller 122 associated with and controlling theservice processors 115 that are inside the devices 100 using theservice. In some embodiments, the service controller 122 requires only anon-real time relatively low data rate secure control planecommunication link to the service processors 115. Accordingly, in someembodiments, the service controller 122 servers can reside in anynetwork that can connect to (e.g., be in network communication with) theInternet 120. For example, this approach provides for a more efficientprovisioning of the equipment used to set up an MVNO partnership betweenthe central provider and the service provider, and as shown in FIG. 2,an MVNO network 210 is in network communication with the Internet 120just as with the central provider network 110 is in networkcommunication with the Internet 120. As shown, the following areconnected to (e.g., in network communication with) the MVNO core network210: MVNO billing system 123, MVNO service controller 122, MVNO contentmanagement system 130, MVNO DNS/DHCP server 126, MVNO AAA server 121,and MVNO mobile wireless center 132.

By showing two service controllers 122, one connected to (e.g., innetwork communication with) the MVNO network 210 and one connected tothe central provider network 110, FIG. 2 also illustrates that someembodiments allow two entities on the same access network to each usethe service controller 122 and service processor 115 to controldifferent devices and offer different or similar services. As describedbelow, the unique secure communication link pairing that exists betweenthe two ends of the service control link, 1691 and 1638 (as shown inFIG. 16), ensure that the two service controllers 122 can only controlthe devices associated with the correct service provider serviceprofiles.

FIG. 3 illustrates another simplified (e.g., “flattened”) networkarchitecture including two central providers in accordance with someembodiments. For example, this provides for roaming agreements whilemaintaining rich services across different networks with completelydifferent access layers. As shown, the mobile devices 100 are assumed tohave a dual mode wireless modem that will operate on both a 4G network,for example LTE or WiMax, and a 3G network, for example HSPA or EVDO.One example roaming condition would be both Central Provider #1 andCentral Provider #2 providing 3G and 4G network resources. In thisexample, the mobile devices 100 can connect to both 3G and 4G basestations 125 owned and operated by the central provider with whom theyhave signed up for service, or when neither is available from thecentral provider the user signed up with the device can roam onto theother central provider access network and still potentially offer thesame rich service set using the same service profiles provided, forexample, the roaming service costs are reasonable. In some embodiments,if roaming service costs are significantly more expensive than homenetwork service costs, then the service processor 115 is configured witha roaming service profile that reduces or tailors service usage orservice activity through a combination of one or more of usernotification, user preference feedback regarding traffic shaping orservice policy management preference collected and acted on by serviceprocessor 115, adaptive policy control in service processor 115 thattracks increasing roaming service costs and scales back service, orrecognition of the change in network that causes the service controller122 to configure service processor 115 of device 100 with a roamingservice profile. In some embodiments, in roaming situations, networkselection can be based on an automatic network selection with networkselection being determined, for example, by a combination of userservice profile preferences, service provider roaming deals and/oravailable roaming network capabilities and cost, as discussed furtherbelow.

In some embodiments, the devices 100 are again assumed to be multimode3G and 4G devices (e.g., the mobile devices 100 are assumed to have adual mode wireless modem that will operate on both a 4G network, forexample LTE, and a 3G network, for example HSPA or EVDO), with thedevices 100 being billed for service by Central Provider #1 being, forexample, EVDO and LTE capable, and the devices 100 being billed forservice by Central Provider #2 being, for example, HSPA and LTE capable.For example, the devices 100 can roam using the 4G LTE network of theroaming central provider when neither the 3G nor 4G networks areavailable with the home central provider. As similarly discussed abovewith respect to the above described roaming embodiments, the serviceprocessors 115 and service controllers 122 are capable of providingsimilar services on the 4G roaming network and the 3G home network as onthe 4G home network, however, the varying costs and available networkcapacity and speed differences of 3G home, 4G roaming and 4G home mayalso encourage the use of different, such as three different, serviceprofiles to allow for the most effective and efficient selection andcontrol of services based on the current network.

FIG. 4 illustrates a network architecture including a Universal MobileTelecommunications System (UMTS) overlay configuration in accordancewith some embodiments. As shown, FIG. 4 includes a 4G/3G/2GHSPA/Transport access network operated by a central provider and twoMVNO networks 210 operated by two MVNO partners. In some embodiments,the central provider can offer improved service capabilities using aconventional UMTS network. As shown, the base stations 125 do notconnect directly to the Internet 120, and instead the base stations 125connect to the conventional UMTS network. However, as in variousprevious embodiments, the service processor 115 still connects throughthe secure control plane link to service controller 122. In someembodiments, the data plane traffic is backhauled across the variousUMTS network routers and gateways as is the control plane traffic, andthe IPDRs are obtained from the access network AAA server 121. Referringnow to the 4G/3G/2G HSPA/Transport access network as shown in FIG. 4,the LTE/HSPA and HSPA/GPRS base stations/nodes 125 are in communicationwith 4G/3G/2G Service/Serving GPRS Support Nodes (SGSNs) cluster 410 viaa radio access network 405, which are in communication with 4G/3G/2GGateway GPRS Support Nodes (GGSNs) cluster 420 via an access transportnetwork 415 (e.g., a GPRS-IP network), which are then in communicationwith central provider core network 110.

As shown in FIG. 4, as discussed elsewhere, service usage data store 118is a functional descriptor for a network level service usage informationcollection and reporting function located in one or more of thenetworking equipment boxes attached to one or more of the sub-networksin the Figure (e.g., RAN, transport and/or core networks). As shown inFIG. 4, service usage 118 is shown as an isolated function connected tothe central provider core network 110 and the intention of thisdepiction is to facilitate all the possible embodiments for locating theservice usage 118 function. In some UMTS network embodiments, theservice usage 118 function is located or partially located in the GGSNgateway (or gateway cluster) 420. In some embodiments, service usage 118functionality is located or partially located in the SGSN gateway (orgateway cluster) 410. In some embodiments, service usage 118functionality is located or partially located in the equipment clusterthat includes the AAA 121 and/or the mobile wireless center 132. In someembodiments, service usage 118 functionality is located or partiallylocated in the base station, base station controller and/or base stationaggregator, collectively referred to as base station 125 in FIG. 4 andmany other figures described herein. In some embodiments, service usage118 functionality is located or partially located in a networkingcomponent in the transport network 415, a networking component in thecore network 110, the billing system 123 and/or in another networkcomponent or function. This discussion on the possible locations for thenetwork based service usage history logging and reporting function canbe easily generalized to all the other figures described herein by oneof ordinary skill in the art (e.g., RAN Gateway 410 and/or TransportGateway 420), and this background will be assumed even if not directlystated in all discussion above and below.

In some embodiments, a central provider provides open developmentservices to MVNO, Master Value Added Reseller (MVAR) and/or OriginalEquipment Manufacturer (OEM) partners. In some embodiments, all threeservice providers, central provider service provider, MVNO #1 serviceprovider and MVNO #2 service provider have service control and billingcontrol of their own respective devices 100 through the unique pairingof the service processors 115 and service controllers 122. For example,MVNO #1 and MVNO #2 can each have open development billing agreementswith the central provider and each can own their respective billingsystems 123. As shown in FIG. 4, MVNO #1 core network 210 is incommunication with the central provider core network 110 via theInternet 120, and MVNO #2 core network 210 is in communication with thecentral provider core network 110 via an alternate landline(LL)/VPNconnection 425. In some embodiments, the two MVNOs each offer completelydifferent devices and/or services, and the devices and/or services alsodiffer significantly from those offered by the central provider, and theservice profiles are adapted as required to service the differentdevices and respective service offerings. In addition, the centralbilling system 123 allows all three service provider user populations toaccess ecommerce experiences from transaction provider partnersoperating transaction servers 134, to choose central provider billingoptions that combine their third party transaction bills on theirservice provider bill, and each subscriber population can experience aservice provider specified look and feel that is unique to therespective service provider even though the different user populationsare interfacing to the same transaction servers and the transactionpartners do not need to require significant custom development toprovide the unique central billing and unique consistent user experiencelook and feel.

In some embodiments, a central provider offers open network device andservice developer services using one service controller server 122(e.g., a service controller server farm) and allows the open developmentpartners to lease server time and server tools to build their ownservice profiles. The central provider also provides service billing onbehalf of services to the open development partners. For example, thisreduces costs associated with setting up an MVNO network for the opendevelopment partners and does not require the partners to give upsignificant control or flexibility in device and/or service control.

FIG. 5 illustrates a network architecture including an Evolution DataOptimized (EVDO) overlay configuration in accordance with someembodiments. This figure is similar to FIG. 4 except for the variousparticular variations of the EVDO network architecture as compared tothe HSPA/GPRS wireless access network architecture as will be apparentto one of ordinary skill in the art. As shown, FIG. 5 includes an EVDOaccess network operated by a central provider and two MVNO networks 210operated by two MVNO partners. The EVDO access network includes LTE/EVDOand EVDO/1×RTT base stations 125 in communication with Base StationController (BSC) packet control 508 and radio network controller 512 viaa radio access network (RAN) 505, which are in communication with packetdata service node 520 via an access transport network 515, which is incommunication with central provider core network 110. As shown, a RANAAA server 521 is also in communication with the access transportnetwork 515.

In some embodiments, the central provider can offer improved servicecapabilities using a wireless access network. As shown, the basestations 125 do not connect directly to the Internet 120, and insteadthe base stations 125 connect to the wireless access network. However,as in various previous embodiments, the service processor 115 stillconnects through the secure control plane link to service controller122. In some embodiments, the data plane traffic is backhauled as shownacross the various network routers and gateways as is the control planetraffic, and the IPDRs are obtained from the access network AAA server121.

FIG. 6 illustrates a network architecture including a 4G LTE and Wi-Fioverlay configuration in accordance with some embodiments. This figureis also similar to FIG. 4 except for the various particular variationsof the 4G LTE/Wi-Fi network architecture as compared to the HSPA/GPRSwireless access network architecture as will be apparent to one ofordinary skill. As shown, FIG. 6 includes a 4G LTE and Wi-Fi accessnetwork operated by a central provider and two MVNO networks 210operated by two MVNO partners. The 4G LTE/Wi-Fi access network as shownincludes LTE eNodeB and HSPA/EVDO base stations 125 in communicationwith Base Station Controller (BSC) packet control (EVDO & 1×RTT) 608 andSGSN (HSPA & GPRS) 612 via a radio access network (RAN) 605, which arein communication with System Architecture Evolution (SAE) Gateway (GW)620 via an access transport network 615, which is then in communicationwith central provider (core) network 110. As shown, a Mobile ManagementEntity (MME) server 619 is also in communication with the accesstransport network 615. Also as shown, a Wi-Fi Access Point (AP) 602 isalso in communication with the access transport network 615 via Wi-FiAccess Customer Premises Equipment (CPE) 604. As will be apparent tothose of ordinary skill in the art, the embodiments of networkarchitectures shown, for example, in FIGS. 1-8 are exemplary networkarchitecture embodiments in which one or more of the shown networkelements may not be required or included, alternative network elementsincluded, and/or additional network elements included based on networkdesign choices, network standards and/or other functional/designconsiderations and choices.

In some embodiments, the central provider can offer improved servicecapabilities using the wireless access network as depicted in FIG. 6. Asshown, the base stations 125 do not connect directly to the Internet120, and instead the base stations 125 connect to the wireless accessnetwork. However, as in various previous embodiments, the serviceprocessor 115 still connects through the secure control plane link toservice controller 122. In some embodiments, the data plane traffic isbackhauled as shown across the various network routers and gateways asis the control plane traffic, and the IPDRs are obtained from the accessnetwork AAA server 121. Accordingly, as shown in FIGS. 4 through 6,various embodiments can be implemented independent of the wirelessaccess network technology, and for example, can be implemented in 3G, 4Gand any other wireless access network technology.

FIG. 7 illustrates a network architecture including a WiMax and Wi-Fioverlay configuration in accordance with some embodiments. This figureis also similar to FIG. 4 except for the various particular variationsof a combined WiMax/Wi-Fi network as compared to the HSPA/GPRS wirelessaccess network architecture as will be apparent to one of ordinary skillin the art. As shown, FIG. 7 includes both a WiMax and Wi-Fi network(e.g., a combined WiMax/Wi-Fi network) operated by a central providerand two MVNO networks 210 operated by two MVNO partners. Although theWi-Fi and WiMax access technologies are different wireless accessnetworking technologies, with WiMax providing a wide area networkingtechnology and Wi-Fi providing a local area networking technology, whichefficiently operates using the two wireless access networkingcapabilities. As similarly discussed above with respect to the switchingbetween 3G and 4G networks, some embodiments employ the automaticnetwork selection capability as described above to choose the bestavailable network service profile, and, for example, the user can forcethe decision or the service controller can make the decision. Forexample, if free Wi-Fi services have adequate coverage, in most cases,the decision criteria programmed into the automatic network selectionalgorithm will select Wi-Fi as long as the Wi-Fi access points areassociated with a known and trusted provider. In some embodiments,transaction billing from central provider billing system 123 or MVNO #1or MVNO #2 billing systems 123 will work with the transaction serverswhen connected over Wi-Fi just as when connected over any other accesstechnology (including wire line based connections). The WiMax/Wi-Fiaccess network as shown includes WiMax base stations 125, Wi-Fi accesspoints/hotspots 702 and/or Wi-Fi mesh access networks 702 (in someembodiments, femto cells can be used in addition to and/or as analternative to Wi-Fi), and Wi-Fi access customer-premises equipment(CPE) 704 in communication with WiMax service controller 708 and Wi-Fiservice controller 712 via a radio access network 705, which are incommunication with WiMax core gateway 720 via an access transportnetwork 715, which is then in communication with central provider (core)network 110.

In some embodiments, the central provider can offer improved servicecapabilities using the wireless access network as depicted in FIG. 7. Asshown, the base stations 125 do not connect directly to the Internet120, and instead the base stations 125 connect to the wireless accessnetwork. However, as in various previous embodiments, the serviceprocessor 115 still connects through the secure control plane link toservice controller 122. In some embodiments, the data plane traffic isbackhauled as shown across the various network routers and gateways asis the control plane traffic, and the IPDRs are obtained from the accessnetwork AAA server 121.

Referring to FIG. 7, the Wi-Fi connection can be replaced with a femtocell (and the Wi-Fi modem shown in FIGS. 15B(3) and 15B(4) can bereplaced with a femto cell modem (base station side functionality)). Insome embodiments, the service processor 115 is provided on the femtocell to control subscriber access in a verifiable manner as similarlydescribed herein with respect to various embodiments (e.g., the Wi-Firelated embodiments). For example, the femto cell service provider(e.g., the entity that owns the spectrum the femto cell is using) canoperate the femto cell as a local access mechanism for the homesubscriber (or other who purchased or installed the femto cell), andthen also use it to provide pay-for-service or additional free services,with controlled access and/or traffic control and/or service controland/or billing control performed locally or in combination with networkequipment as described herein. In some embodiments, the WWAN devicesbeing used at home or work with the femto cell include a portion of theservice processor functionality. For example, this allows the serviceprovider for femto cells to provide service and monetize service in acontrolled way even though the femto cell is not connected to theservice provider network the way conventional base stations areconnected to the service provider network, but is connected through theInternet 120. For example, the secure heartbeat function can be extendedto include data traffic so that it is encrypted and secured along withthe control plane traffic. The decision of whether or not to admit adevice onto the femto cell can be made through the service processor 115connection to the service controller 122 and subsequent look up of thecredentials for the device and the associated service plan and serviceprofile that is then programmed into the service processor on the femtocell and/or the device itself. The femto cell can also offer a landingpage to devices through the service processor so that devices that donot belong to the network can gain access to the network by signing upover the femto cell. For example, the intermediate device embodimentsfor Wi-Fi on one end and WWAN on the other can be accomplished by usingthe Wi-Fi connection in the cell phone in AP mode so that it becomes theintermediate device. The service processor 115 on the cell phone canthen act in the same manner as described for the intermediate device asdescribed herein.

FIG. 8 illustrates another simplified (e.g., “flattened”) networkarchitecture including multiple wireless access networks (e.g., 3G and4G Wireless Wide Area Networks (WWANs)) and multiple wire line networks(e.g., Data Over Cable Service Interface Specification (DOCSIS) andDigital Subscriber Line Access Multiplexer (DSLAM) wire line networks)in accordance with some embodiments. It is a common network architecturefor multi-access central providers to have one or more wired accessnetworks and one or more wireless access networks. As shown, FIG. 8includes both 3G and 4G wireless access networks, including a 4G basestation 125 and a 3G base station 125, and both DOCSIS and DSLAM wireline networks (e.g., a combined WWAN/wire line network), includingDOCSIS Head End 125 and DSLAM 125, operated by a central provider viacentral provider (core) network 110 and an MVNO partner via MVNO network210 via the Internet 120.

As shown, the service processor 115 can reside on a number of differenttypes of devices 100 that work on 3G or 4G wireless, DSL or DOCSIS, andthe service controller 122 is capable of controlling each of these typesof devices with a consistent service experience, for example, usingdifferent service profiles, service capabilities and service profilecost options depending on which network the device is connected toand/or other criteria. For example, a download of a High Definition (HD)movie can be allowed when the service controller 122 is managing serviceprofile policies for a service processor 115 residing on a DOCSIS device100 (e.g., a computer or laptop connected to a cable modem), but notwhen the same service controller 122 is managing service profilepolicies for a service processor 115 residing on a 3G device 100 (e.g.,a smart phone connected to a mobile 3G network).

As will now be apparent to one of ordinary skill in the art in view ofthe above description of FIGS. 1 through 8, the present invention can beprovided across any access network and a set of service profiles can bedefined in a variety of ways including, for example, to user preferencefeedback, access network performance, access network cost, accessnetwork central provider partnership status with the service providercentral provider and roaming deals and costs. For example, as discussedbelow, various embodiments allow for users to have superior serviceexperiences based on the ability to control certain of their servicesettings, and service providers can also more efficiently deploy agreater variety of services/service plans to users.

In some embodiments, the service processor 115 and the servicecontroller 122 provide an overlay for existing networks withoutsignificantly changing the billing system 123, gateways/routers or othernetwork components/elements, and also provide verifiable servicemonitoring to control services and/or service usage/costs withoutinvolving, for example, a service provider or MVNO (e.g., for smartphone devices and/or laptops or netbooks (or any other networkaccessible device) with an unlimited data plan or any other serviceplan). For example, applications that are deployed by device owners orservice subscribers (e.g., an IT manager) and do not involve a serviceprovider include roaming services provided as an after-market productwithout carrier/service provider involvement. In this example, deviceactivity is recorded by the service processor 115 and transmitted to theservice controller 122 (e.g., the IT manager controls the servicecontroller 122). In another example, a third party after-market productis provided in which the service controller 122 is hosted by the thirdparty and the device management entity (e.g., the IT manager or parentsof the device user for parental controls) uses a secure Virtual ServiceProvider (VSP) website to control the devices that belong to thatmanagement entity's device partition (e.g., VSP partitions andtechniques are described below with respect to FIG. 49). The VSP securewebsite techniques described herein can also be applied to serviceprovider owned servers with device partitions for the purpose ofcontrolling, for example, Deep Packet Inspection (DPI) controllers(e.g., DPC policy implementation 5402 as shown in FIG. 54) to providesimilar or substantially equivalent service usage/control capabilitiesusing network based service control techniques, as similarly describedin detail below with respect to FIGS. 49 and 54 (e.g., IT manager VSPcontrol of a group partition and/or MVNO VSP control of a grouppartition).

Service Processor Configurations for Devices

FIG. 9 illustrates a hardware diagram of a device 100 that includes aservice processor 115 in accordance with some embodiments. As shown inFIG. 9, the service processor 115 is stored in a non volatile memory 910and a memory 920 of the device 100. As will be appreciated by those ofordinary skill in the art, the present invention can operate withvirtually any device architecture, and the device architecturesdiscussed herein (e.g., with respect to FIGS. 9 through 15) are examplesof various implementations on certain devices (e.g., of differentrepresentations of device 100).

As shown in FIG. 9, device 100 also includes a processor 930, sometimesreferred to as a CPU or central processor unit, an APU or applicationprocessor unit, a core processor, a computing device, or many other wellknown terms. In some embodiments, device 100 includes one or moreprocessors and/or a multicore processor. As shown, processor 930includes a sub-processor 935. In some embodiments, processor 930 and/orsub-processor 935 are based on an architecture sometimes referred to asa complex instruction set computer or CISC, a reduced instruction setcomputer or RISC, a parallel processor, a combination of two or morearchitectures or any other processor architecture. In some embodiments,processor 930 has a design that is based on logic and circuitry from oneor more standard design library or published architecture, or includesspecialized logic and circuitry designed for a given device 100 orcollection of such devices. In some embodiments, a device includes morethan one processor and/or sub-processor, and in such a device, oneprocessor and/or sub-processor can have one architecture while anothermay have a somewhat different or completely different architecture. Insome embodiments, one or more of the processors and/or sub-processorscan have a general purpose architecture or instruction set, can have anarchitecture or instruction set that is partially general or partiallyspecialized, or can have an instruction set or architecture that isentirely specialized. In some embodiments, a device includes more thanone processor and/or sub-processor, and in such a device, there can be adivision of the functionality for one or more processors and/orsub-processors. For example, one or more processors and/orsub-processors can perform general operating system or applicationprogram execution functions, while one or more others can performcommunication modem functions, input/output functions, user interfacefunctions, graphics or multimedia functions, communication stackfunctions, security functions, memory management or direct memory accessfunctions, computing functions, and/or can share in these or otherspecialized or partially specialized functions. In some embodiments, anyprocessor 930 and/or any sub-processor 935 can run a low level operatingsystem, a high level operating system, a combination of low level andhigh level operating systems, or can include logic implemented inhardware and/or software that does not depend on the divisions offunctionality or hierarchy of processing functionality common tooperating systems.

As shown in FIG. 9, device 100 also includes non-volatile memory 910,memory 920, graphics memory 950 and/or other memory used for generaland/or specialized purposes. As shown, device 100 also includes agraphics processor 938 (e.g., for graphics processing functions). Insome embodiments, graphics processing functions are performed byprocessor 930 and/or sub-processor 935, and a separate graphics process938 is not included in device 100. As shown in FIG. 9, device 100includes the following modems: wire line modem 940, WWAN modem 942, USBmodem 944, Wi-Fi modem 946, Bluetooth modem 948, and Ethernet modem 949.In some embodiments, device 100 includes one or more of these modemsand/or other modems (e.g., for other networking/access technologies). Insome embodiments, some or all of the functions performed by one or moreof these modems are performed by the processor 930 and/or sub processor935. For example, processor 930 can implement some or all of certainWWAN functional aspects, such as the modem management, modem physicallayer and/or MAC layer DSP, modem I/O, modem radio circuit interface, orother aspects of modem operation. In some embodiments, processor 930 asfunctionality discussed above is provided in a separate specializedprocessor as similarly shown with respect to the graphics and/ormultimedia processor 938.

As also shown in FIG. 9, device 100 includes an internal (or external)communication bus structure 960. The internal communication busstructure 960 generally connects the components in the device 100 to oneanother (e.g., allows for intercommunication). In some embodiments, theinternal communication bus structure 960 is based on one or more generalpurpose buses, such as AMBA, AHP, USB, PCIe, GPIO, UART, SPI, I²C, Firewire, DisplayPort, Ethernet, Wi-Fi, Bluetooth, Zigbee, IRDA, and/or anyother bus and/or I/O standards (open or proprietary). In someembodiments, the bus structure is constructed with one or more customserial or parallel interconnect logic or protocol schemes. As will beapparent to one of ordinary skill in the art, any of these or other busschemes can be used in isolation and/or in combination for variousinterconnections between device 100 components.

In some embodiments, all or a portion of the service processor 115functions disclosed herein are implemented in software. In someembodiments, all or a portion of the service processor 115 functions areimplemented in hardware. In some embodiments, all or substantially allof the service processor 115 functionality (as discussed herein) isimplemented and stored in software that can be performed on (e.g.,executed by) various components in device 100. FIG. 9 illustrates anembodiment in which service processor 115 is stored in device memory, asshown, in memory 920 and/or non-volatile memory 910, or a combination ofboth. In some embodiments, it is advantageous to store or implementcertain portions or all of service processor 115 in protected or securememory so that other undesired programs (and/or unauthorized users) havedifficulty accessing the functions or software in service processor 115.In some embodiments, service processor 115, at least in part, isimplemented in and/or stored on secure non-volatile memory (e.g., nonvolatile memory 930 can be secure non-volatile memory) that is notaccessible without pass keys and/or other security mechanisms. In someembodiments, the ability to load at least a portion of service processor115 software into protected non-volatile memory also requires a securekey and/or signature and/or requires that the service processor 115software components being loaded into non-volatile memory are alsosecurely encrypted and appropriately signed by an authority that istrusted by a secure software downloader function, such as servicedownloader 1663 as discussed below (and as shown in FIG. 16). In someembodiments, a secure software download embodiment also uses a securenon-volatile memory. Those of ordinary skill in the art will alsoappreciate that all memory can be on-chip, off-chip, on-board and/oroff-board. In some embodiments, the service processor 115 which as shownin FIG. 9 is stored or implemented in non volatile memory 910 and memory920, can be implemented in part on other components in device 100.

As shown, device 100 also includes a user interfaces device component980 for communicating with user interface devices (e.g., keyboards,displays and/or other interface devices) and other I/O devices component985 for communicating with other I/O devices. User interface devices,such as keyboards, display screens, touch screens, specialized buttonsor switches, speakers, and/or other user interface devices providevarious interfaces for allowing one or more users to use the device 100.

FIG. 10 illustrates another hardware diagram of a device 100 thatincludes a service processor 115 in accordance with some embodiments. Asshown in FIG. 10, the service processor 115 is implemented on theprocessor 930 of the device 100. In some embodiments, thisimplementation can be in part or whole accomplished in software stored,implemented and/or executed on the processor 930. In some embodiments,the implementation and/or execution can be in part or whole accomplishedin hardware that is on the processor 930. While the service processor115 is shown in FIG. 10 as stored, implemented and/or executed on theprocessor 930, in other embodiments, the service processor 115 isimplemented in part on other components in device 100, for example, asdiscussed below.

Service Processor Implemented on a Communications Modem

FIG. 11 illustrates another hardware diagram of a device 100 thatincludes a service processor 115 in accordance with some embodiments. Asshown in FIG. 11, the service processor 115 is implemented on the WWANmodem 942 of the device 100. In some embodiments, this implementationcan be in part or whole accomplished in software stored, implementedand/or executed on the WWAN modem 942. In some embodiments, theimplementation and/or execution can be in part or whole accomplished inhardware that is on the WWAN modem 942. In some embodiments, serviceprocess 115 is implemented on another modem component of device 100and/or one or more of the modem components of device 100.

In some embodiments, the service processor 115 is implemented on a modemprocessor (e.g., WWAN modem 942 or WWAN/Wi-Fi modem), and the serviceprocessor 115 can be installed and/or executed in protected and/orsecure memory or processor hardware on the modem. The modem memory canbe made robust to hacking or tampering and, in some embodiments, is onlyaccessible from a secure network management channel or secure devicemanagement port and not by most end users. In some embodiments, aportion of the service processor 115 is implemented on a modem processor(e.g., WWAN modem 942 hardware or software), and a portion of theservice processor 115 is implemented on another device 100 processor930. For example, the device service monitor agent 1696 and one or moreservice usage measurement points (see discussion associated with FIG.21) can be implemented on a modem processor, and other service processor115 elements can be implemented in the main device operating systemprocessor 930. As another example, a second (or first) service monitoragent 1696 and one or more service usage measurement points can beimplemented on a modem processor, and a first (or second) servicemonitor 1696 with one or more service measurement points can beimplemented on the main operating system processor 930 for device 100.For example, such embodiments can be configured to provide a serviceusage measurement and reporting system that offers a diversifiedcountermeasure to protect against hacking, tampering or other errors fordevice based service usage measurements that can be made harder to hackor tamper with than certain software embodiments on the processor 930.For example, such embodiments can be employed when one or more of thefollowing capabilities are not available: network based service usagemeasures, network based service profile or policy implementationverification measures, and network based service usage verificationerror response action capabilities.

In some embodiments, certain portions of the service processor 115 thatdeal with application layer service monitoring or traffic flowidentification (e.g., tagging or traffic flow shaping as disclosedelsewhere) are implemented on a main processor 930, and other portionsof the service processor 115 are implemented on a modem processor (e.g.,WWAN modem 942).

In some embodiments, the WWAN modem is a wide area access technologymodem such as 2G, 2.5G, 3G or 4G. As discussed above and below, theconnection to the WWAN modem 942 can be a connection internal to device100, for example a USB, GPIO, AMBA or other bus, or can be a connectionthat extends external to the device such as for example a USB, Ethernet,Wi-Fi, Bluetooth or other LAN or PAN connection. Three exampleembodiments in which the bus is internal to the device are as follows: aPCIe modem card running over USB or PCIe, a GPIO connection running froma processor 930 chipset to a modem chipset inside a mobile device, or aWi-Fi connection running from a Wi-Fi modem inside of device 100 to anintermediate modem or networking device combination that forwards theaccess network traffic between the access network connection and thedevice via the Wi-Fi connection. In some embodiments, in addition to theservice processor 115 being implemented on the WWAN modem 942 eitherinternal or external to the device 100, similarly service processor 115can be implemented on a wire line modem 940, such as DSL, Cable orfiber, another wireless LAN or PAN modem, such as Wi-Fi, Zigbee,Bluetooth modem 948, White Space, or some other modem, connectedinternal to device 100 or external to device 100 via a LAN or PANextension of internal or external communications bus structure 960.

In some embodiments, a complete turn-key reference design product forthe device modem (one or more of 942, 946, 948, 949, 944, 940) combinedwith a built-in service processor 115, possibly with a well defined anddocumented application interface and a well defined and documentedservice processor developers kit (SPDK) provides for a powerful productembodiment for the purpose of achieving mass market distribution andusage for the modem with service processor 115 and associated servicecontroller 122 features. For example, embodiments that include the WWANmodem 942, possibly in combination with one or more additional modemsincluding Wi-Fi modem 946, bluetooth modem 948, USB modem 944 andEthernet modem 949, can be combined with a pre-tested or pre-certifiedintegrated embodiment of the service processor 115, possibly incombination with a well defined API for writing software applicationsthat interface to, reside on or communicate with this turn-key modemembodiment. As disclosed herein, the advantageous capabilities of theservice processor 115, possibly in conjunction with the servicecontroller 122, to assist in monitoring, control, billing andverification for services is made more available for device 100manufacturers in such a form, because the manufacturers do not need tospend as much time and resources to develop a custom modem only for asubset of devices that the turn-key modem can be used to support. Insome embodiments, the service processor 115, as discussed herein, can beconfigured to provide device assisted service monitoring, control,billing and/or verification across not just when connected to the WWANnetwork via the WWAN modem, but also when connected to the othernetworks corresponding to the other access modems included in theturn-key combined module plus service processor 115 (or SPDK or chipsetplus service processor 115) design. The pre-integrated service processor115 and API possibly in combination with testing and certification canbe packaged in a small form factor that may have standardized interfacessuch as USB, PCIe, firewire, Display Port, GPIO, or other interface. Theform factor may be miniaturized into standard configurations such asminicard, half minicard or even smaller form factors, or it can bedesigned into a non-standard or proprietary form factor. The module formfactor can be well documented to simplify integration into variousdevice 100 designs. The SPDK embodiments can be designed to contain oneor more of the following: hardware integration and use documentation,software integration documentation, software programming documentation,application interface documentation, service controller documentation,overall testing guidelines and overall use guidelines. In someembodiments, the modem module can be integrated with the serviceprocessor 115 functionality as a combined chipset, firmware and/orsoftware product, with other SPDK features very similar to those listedabove. The service controller programming guide for these turn-keyembodiments can also be documented for the SPDK service processor 115software, turn-key module with service processor 115 or integratedchipset with service processor 115. Accordingly, these embodimentsprovide various solutions to simplify the OEM task of integrating,developing, testing and shipping device 100 products (or integratednetworking device products) with any of the device assisted servicemonitoring, control, billing or verification capabilities disclosedherein.

FIG. 12 illustrates another hardware diagram of a device 100 thatincludes a service processor 115 in accordance with some embodiments. Asshown in FIG. 12, the service processor 115 is implemented on the otherI/O devices component 980 of the device 100. In some embodiments, thisimplementation can be in part or whole accomplished in software stored,implemented and/or executed on the other I/O devices component 980(e.g., a SIM/USIM card or other secure hardware I/O device). In someembodiments, the implementation and/or execution can be in part or wholeaccomplished in hardware that is on the other I/O devices component 980.

As discussed above, various embodiments include product designs in whichthe service processor 115 resides on device volatile or non-volatilememory (see FIG. 9), the device application processor or CPU (see FIG.10), the wireless access modem (see FIG. 11) (or any other modem), oranother I/O device (see FIG. 12). While these are just a few of theexample service processor 115 placement embodiments, these embodimentsshow that the placement of where the software or hardware forimplementing the service processor 115 can reside in the device 100 isvery flexible and can be implemented in a myriad of places and waysdepending on the device and/or other technical design choices.

FIG. 13 illustrates another hardware diagram of a device 100 thatincludes a service processor 115 implemented in external memory of aSystem On Chip (SOC) 1310 in accordance with some embodiments. As shownin FIG. 13, the service processor 115 is implemented on the externalmemory 1320 of the device 100. In some embodiments, this implementationcan be in part or whole accomplished in software stored, implementedand/or executed on the external memory 1320. In some embodiments, theimplementation and/or execution can be in part or whole accomplished inhardware that is on the external memory 1320. In some embodiments, SOCchipset 1310 and external memory 1320 provide a portion or all of thehardware of device 100.

FIG. 14 illustrates another hardware diagram of a device 100 thatincludes a service processor 115 implemented in external memory of aSystem On Chip (SOC) 1310 in accordance with some embodiments. As shown,the service processor 115 is stored in a non volatile memory 910 and amemory 920 of the SOC chipset 1310, as similarly discussed above withrespect to FIG. 9. In some embodiments, SOC chipset 1310 and externalmemory 1320 provide a portion or all of the hardware of device 100.

As similarly discussed above with respect to FIGS. 9 through 12, variousembodiments include product designs including the SOC chipset 1310 inwhich the service processor 115 resides on internal volatile ornon-volatile memory 910 of the SOC chipset 1310 (see FIG. 14), thedevice application processor or CPU 930 and/or sub processor 935, themodems 940, 942, 944, 946, 948, and/or 949 (or any other modem), anotherI/O device 985, and/or external memory 1320 (see FIG. 13) (and/or anycombinations thereof). While these are just a few of the example serviceprocessor 115 placement embodiments, these embodiments show that theplacement of where the software or hardware for implementing the serviceprocessor 115 can reside in the SOC chipset 1310 and/or the externalmemory 1320 of the device 100 is very flexible and can be implemented ina myriad of places and ways depending on the device and/or othertechnical design choices.

The above discussion with respect to FIGS. 9 through 14 illustratingvarious internal hardware embodiments for device 100 applies equally tothis partitioning of device functionality or any other partitioning ofhow the components in device 100 are configured, whether they are allseparate components, some of the components are combined into a singlechipset but there are still multiple chipsets, or all of the componentsare combined into a chipset. For example, FIGS. 9 through 14illustrating various internal hardware embodiments for device 100 showseveral access modem components including the wire line modem 940,wireless wide area network (WWAN) modem 942, USB modem 944, Wi-Fi modem946, Bluetooth modem 948, and Ethernet modem 949. In some embodiments,wire line modem 940 is a DSL or cable modem such as DOCSIS, or someother modem with a hard connection such as fiber. In some embodiments,as discussed above and below, connection to the wire line or wirelessaccess network is accomplished through an extension of the internal orexternal communications bus structure 960. For example, such anextension is accomplished using one or the other modems, such as Wi-Fimodem 946 or Ethernet modem 949, connecting to a local area network thatin turn connects to the access network via a device that bridges thelocal area network to the access network. One of ordinary skill in theart will appreciate that when discussing device connection to any accessnetwork the connection can be via a direct connection to the network,such as a 3G or 4G WWAN modem 942 connection to a 3G or 4G WWAN network,or can be a connection to the access network through an intermediateconnection, such as a Wi-Fi modem 946 connection to a modem ornetworking device combination that has a Wi-Fi LAN connection and a 3Gor 4G network access network connection. Another example of an extendedmodem connection embodiment includes a Wi-Fi modem 946 device connectionto a modem or networking device combination that includes a Wi-Fi LANconnection and a DOCSIS or DSL network access connection. Other examplesof such combinations will be readily apparent to one of ordinary skillin the art.

Service Processor Configurations for Intermediate Networking Devices

FIGS. 15A through 15C illustrate hardware diagrams of a device 100 thatinclude a service processor 115 and a bus structure extension 1510 usingintermediate modem or networking device combinations in accordance withvarious embodiments. For example, FIGS. 15A and 15B illustrate variousextended modem alternatives for access network connection through anintermediate modem or networking device combination that has aconnection (e.g., LAN connection) to one or more devices 100.

In some embodiments, device 100 includes a 3G and/or 4G network accessconnection in combination with the Wi-Fi LAN connection to the device100. For example, the intermediate device or networking devicecombination can be a device that simply translates the Wi-Fi data to theWWAN access network without implementing any portion of the serviceprocessor 115 as shown in FIG. 15B(1). In some embodiments, anintermediate device or networking device combination includes a moresophisticated implementation including a networking stack and someembodiments a processor, as is the case for example if the intermediatenetworking device or networking device combination includes a routerfunction, in which case the service processor 115 can be implemented inpart or entirely on the intermediate modem or networking devicecombination. The intermediate modem or networking device combination canalso be a multi-user device in which more than one user is gainingaccess to the 3G or 4G access network via the Wi-Fi LAN connection. Inthe case of such a multi-user network, the access network connection caninclude several managed service links using multiple instantiations ofservice processor 115, each instantiation, for example, beingimplemented in whole or in part on device 100 with the intermediatemodem or networking device combination only providing the translationservices from the Wi-Fi LAN to the WWAN access network.

Referring now to FIGS. 15A and 15B(2)-(4), in some embodiments, theservice processors 115 are implemented in part or in whole on theintermediate modem or networking device combination. In the case wherethe service processor 115 is implemented in part or in whole on theintermediate modem or networking device combination, the serviceprocessor 115 can be implemented for each device or each user in thenetwork so that there are multiple managed service provider accounts allgaining access through the same intermediate modem or networking devicecombination. In some embodiments, the functions of service processor 115are implemented on an aggregate account that includes the WWAN accessnetwork traffic for all of the users or devices connected to the Wi-FiLAN serviced by the intermediate modem or networking device combination.In some embodiments, the central provider can also provide an aggregatedaccount service plan, such as a family plan, a corporate user group planand/or an instant hotspot plan. In the case where there is one accountfor the intermediate modem or networking device combination, theintermediate modem or networking device combination can implement alocal division of services to one or more devices 100 or users in whichthe services are controlled or managed by the intermediate modem ornetworking device combination or the device 100, but the management isnot subject to service provider control and is auxiliary to the servicemanagement or service policy implementation performed by serviceprocessors 115. In some embodiments, another service model can also besupported in which there is an aggregate service provider planassociated with one intermediate modem or networking device combination,or a group of intermediate modems or networking device combinations butwhere each user or device still has its own service plan that is asub-plan under the aggregate plan so that each user or device hasindependent service policy implementation with a unique instantiation ofservice processor 115 rather than aggregate service policyimplementation across multiple users in the group with a singleinstantiation of service processor 115.

As shown in FIG. 15A and 15B(2), in some embodiments, device 100includes a Wi-Fi modem 946, a Wi-Fi modem 946 combined with a 3G and/or4G WWAN modem 1530 on intermediate modem or networking devicecombination 1510, and the intermediate modem or networking devicecombination forwards WWAN access network traffic to and from device 100via the Wi-Fi link. For example, the service processor 115 can beimplemented in its entirety on device 100 and the service provideraccount can be associated exclusively with one device. This is anembodiment associated with one or more of FIGS. 29, 31, 32 or 34discussed below, in which the modem bus represents the Wi-Fi LANconnection via the Wi-Fi modem 946. Similarly, as shown in FIGS. 15A and15B(3), such an implementation can be provided using a different accessmodem and access network, such as a 2G and/or 3G WWAN, DSL wire line,cable DOCSIS wire line or fiber wire line configuration in place of the3G and/or 4G access network connection to the intermediate modem ornetworking device combination 1510. In addition, various otherembodiments similarly use DSL as shown in FIGS. 15A and 15B(4), USB,Ethernet, Bluetooth, or another LAN or point to point connection fromdevice 100 to the intermediate modem or networking device combination1510.

In some embodiments, a portion of the service processor 115 isimplemented on the device 100, such as the application interface agent1693 and other supporting agents (see FIG. 16), and another portion ofthe service provider 115 is implemented on the intermediate modem ornetworking device combination, such as policy implementation agent 1690or possibly modem firewall 1655 as well as other agents (see FIG. 16).This is an embodiment associated with one or more of FIGS. 30 or 36discussed below, in which the modem bus in the figure represents theWi-Fi LAN connection via the Wi-Fi modem 946. In this example, theservice provider 115 can still offer individual service plans associatedexclusively with one device, or can offer an aggregate plan in which theportion of the service processor 115 located on the intermediate modemor networking device combination 1510 aggregates service plans into oneWWAN connection but each individual device 100 has a unique serviceinterface via the application interface agents and associated agentslocated on device 100. Similarly, such an implementation can be providedusing a different access modem and access network, for example a 2Gand/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire lineconfiguration in place of the 3G and/or 4G access network connection tothe intermediate modem or networking device combination 1510. Inaddition, various other embodiments similarly use USB, Ethernet,Bluetooth, or another LAN or point to point connection from device 100to the intermediate modem or networking device combination 1510.

In some embodiments, all of the service processor 115 is implemented onthe intermediate modem or networking device combination 1510 and theaggregate device or user traffic demand from the LAN port is servicedthrough one service provider service plan account. This is an embodimentassociated with FIG. 35 in which as discussed below the modem bus in thefigure represents the Wi-Fi LAN connection via the Wi-Fi modem 946.Similarly, such an implementation can be provided using a differentaccess modem and access network, for example a 2G and/or 3G WWAN, DSLwire line, cable DOCSIS wire line or fiber wire line configuration inplace of the 3G and/or 4G access network connection to the intermediatemodem or networking device combination 1510. In addition, various otherembodiments similarly use USB, Ethernet, Bluetooth, or another LAN orpoint to point connection from device 100 to the intermediate modem ornetworking device combination 1510.

In some embodiments, the device 100 uses the on-board WWAN modem 942when it is outside of Wi-Fi LAN coverage area for one or more trustedaccess networks for the device, and when the device comes within rangeof a Wi-Fi network associated with a intermediate modem or networkingdevice combination connected to a trusted wire line access network, thedevice can switch to the Wi-Fi link service to connect service processor115 to the trusted wire line access network. In some embodiments, thedecision to switch to the Wi-Fi LAN associated with a trusted wire lineaccess network can be made automatically by the device based on thepolicy implementation rules settings for the modem selection and control1811 and/or the policy control agent 1692, can be made by the user, orcan be made by the service controller 122 (see FIG. 18). In addition,various other embodiments similarly use USB, Ethernet, Bluetooth, oranother LAN or point to point connection from device 100 to theintermediate modem or networking device combination 1510.

FIG. 15C illustrates another hardware diagram of a device 100 thatincludes a service processor 115 and a bus structure extension 1510using intermediate modem or networking device combinations in accordancewith various embodiments. In some embodiments, more than one accessnetwork connection is implemented in the intermediate modem ornetworking device combination 1510. This allows the device 100 topotentially connect through the intermediate modem or networking devicecombination with a choice of access network services. An example of suchan embodiment is illustrated in FIG. 15C in which an access networkrouter (e.g., an enterprise router) connected to a LAN with a wire lineprimary backhaul connection and a back up WWAN connection, for example3G or 4G, to provide access services when the primary wire lineconnection fails. As discussed above, the service provider serviceprofile for service processor 115 and the service plan account can beset up as an aggregate account with multiple users connected to the LAN.The service provider can elect to use an embodiment that includes aportion of the service processor 115 on each device 100 so that theaccount can be managed for each user or each device, or the serviceprovider can elect to implement all of the necessary features in theservice processor 115 on the intermediate modem or networking devicecombination so that there is no visibility to the individual devices 100or users.

As described herein, various embodiments provide many service policyimplementation options that can enhance the service provider control ofthe service experience and cost, or enhance the user control of theservice experience and cost by providing a verifiable or compromiseresistant solutions to manage service policy implementation on theintermediate modem or networking device combination, for one or both ofthe WWAN or wire line access networks, when the WWAN access network isactive, or when the WWAN access network is inactive. The level ofservice control, user preference feedback and service policyimplementation verification or compromise resistance enabled by theseembodiments improves the offered back up services and primary wire lineservices. One of ordinary skill in the art will also now appreciate thatany number of wire line and/or wireless network access connections canbe supported by the various embodiments as described herein, with anynumber of device architectures and architectures for intermediate modemor networking device combinations bridging the device to the accessnetwork of choice. Accordingly, various embodiments provide a verifiablemanaged service architecture, design and implementation for any numberof single access and/or multi-access networks in which the serviceaccount can be consistent across multiple networks, and the servicepolicies can be changed from network to network as deemed appropriate bythe service provider with service notification, service cost control andprivacy preference inputs from the user.

In various embodiments, the verification embodiments discussed hereinfor service policy implementation verification or service policyimplementation compromise protection can be applied. In someembodiments, rather than attaching a service provider service planaccount to a single device, it is attached to (e.g., associated with) auser. For example, when the user logs onto an access network with aservice controller controlled by a service provider, regardless of whatdevice the user logs onto with the user's service plan profile can beautomatically looked up in the central billing system 123 anddynamically loaded (e.g., downloaded) onto the device 100 from theservice controller 122 (e.g., a service profile provided on demand basedon the user's identity). In some embodiments, in addition to dynamicallyloading the user's service policy implementation and control settings,one or more of the user's preferences including notification, servicecontrol, traffic monitor reporting privacy and Customer RelationshipManagement (CRM) reporting privacy are also dynamically loaded. Forexample, this allows the user to have the same service settings,performance and experience regardless of the device the user is loggedinto and using on the network. In addition, as discussed herein, in thevarious embodiments that call for roaming from one type of accessnetwork to another, the user service plan profile, that includes all ofthe above in addition to the service plan profile changes that takeeffect between different types of access network, can be used on anydevice and on any network, providing the user with a verifiable orcompromise resistant, consistent service experience regardless ofnetwork or device.

Many of the embodiments described herein refer to a user using device100. It is understood that there are also applications for these variousembodiments that do not involve user interfaces. Examples of suchapplications include equipment, apparatus or devices for automation,telemetry, sensors, security or surveillance, appliance control, remotemachine to machine data connections, certain remote accessconfigurations, two way power metering or control, asset tracking,people tracking or other applications in which a human user interface isnot required for device 100.

Various embodiments of the device 100 described above include other I/Odevices 985. In some embodiments, these other devices include othermodems, other special purpose hardware components, and/or other I/Odevices or drivers or modems to connect to other I/O devices. In someembodiments, these other devices include a Subscriber Identity Module(SIM) or Universal Subscriber Identity Module (USIM) device. In someembodiments, it is advantageous to implement some or all of the serviceprocessor 115 functions on an embodiment of device 100 that includes aSIM and/or a USIM. In some embodiments, the other I/O devices 985include a hardware device designed to implement a portion or all of theservice processor 115 functions. For example, this is advantageous incases in which the original device 100 was not manufactured with theservice processor 115; in cases in which dedicated hardware is desiredto improve one or more aspects of service processor 115 performance;allowing users, for example, to have the same service settings,performance and experience regardless of the device the user is using onthe network by using such a SIM and/or USIM (e.g., or implemented as atype of dongle); and/or in cases in which a separate component isdesired to assist in compromise protection for one or more aspects ofservice processor 115.

As discussed above, some embodiments described herein provide forbilling of certain access services. In some embodiments, variousapplications do not require or involve billing of certain services. Forexample, applications like enterprise IT (Information Technology) groupmanagement of enterprise workforce access policy implementation oraccess cost control or access security policy, privacy control, parentalcontrol, network quality of service control or enhancement, privatenetwork services, free access services, publicly funded access services,flat rate no-options service and other services, or other examples thatwill be apparent to one of ordinary skill in the art do not requirebilling functionality but benefit from many other aspects of variousembodiments.

Service Processor and Service Controller for Verifiable ServiceMonitoring, Notification and Control

FIG. 16 is a functional diagram illustrating a device based serviceprocessor 115 and a service controller 122 in accordance with someembodiments. For example, this provides relatively full featured devicebased service processor implementation and service controllerimplementation. As shown, this corresponds to a networking configurationin which the service controller 122 is connected to the Internet 120 andnot directly to the access network 1610. As shown, a data plane (e.g.,service traffic plane) communication path is shown in solid lineconnections and control plane (e.g., service control plane)communication path is shown in dashed line connections. As previouslydiscussed, it is understood that the division in functionality betweenone device agent and another is based on, for example, design choices,networking environments, devices and/or services/applications, andvarious different combinations can be used in various differentimplementations. For example, the functional lines can be re-drawn inany way that the product designers see fit. As shown, this includescertain divisions and functional breakouts for device agents as anillustrative implementation, although other, potentially more complex,embodiments can include different divisions and functional breakouts fordevice agent functionality specifications, for example, in order tomanage development specification and testing complexity and workflow. Inaddition, the placement of the agents that operate, interact with ormonitor the data path can be moved or re-ordered in various embodiments.For example, as discussed below in some embodiments, one or more of thepolicy implementation or service monitoring functions can be placed onone of the access modems located below the modem driver and modem bus inthe communication stack as illustrated in certain figures and describedherein. As discussed below, some simplified embodiment figuresillustrate that not all the functions illustrated in all the figures arenecessary for many designs, so a product/service designer can choose toimplement those functions believed to be most advantageous or sufficientfor the desired purposes and/or environment. The functional elementsshown in FIG. 16 are described below.

As shown, service processor 115 includes a service control device link1691. For example, as device based service control techniques involvingsupervision across a network become more sophisticated, it becomesincreasingly important to have an efficient and flexible control planecommunication link between the device agents and the network elementscommunicating with, controlling, monitoring, or verifying servicepolicy. In some embodiments, the service control device link 1691provides the device side of a system for transmission and reception ofservice agent to/from network element functions. In some embodiments,the traffic efficiency of this link is enhanced by buffering and framingmultiple agent messages in the transmissions. In some embodiments, thetraffic efficiency is further improved by controlling the transmissionfrequency or linking the transmission frequency to the rate of serviceusage or traffic usage. In some embodiments, one or more levels ofsecurity or encryption are used to make the link robust to discovery,eavesdropping or compromise. In some embodiments, the service controldevice link 1691 also provides the communications link and heartbeattiming for the agent heartbeat function. As discussed below, variousembodiments disclosed herein for the service control device link 1691provide an efficient and secure solution for transmitting and receivingservice policy implementation, control, monitoring and verificationinformation with other network elements.

In some embodiments, the service control device link 1691 agent messagesare transmitted asynchronously as they are generated by one or more ofthe service agents. In some embodiments, the service control device link1691 performs collection or buffering of agent messages betweentransmissions. In some embodiments, the service control device link 1691determines when to transmit based potentially on several parametersincluding, for example, one or more of the following parameters:periodic timer trigger, waiting until a certain amount of service usageor traffic usage has occurred, responding to a service controllermessage, responding to a service controller request, initiated by one ormore agents, initiated by a verification error condition, initiated bysome other error or status condition. In some embodiments, once atransmission trigger has occurred, the service control device link 1691assembles all buffered agent communications and frames thecommunications.

In some embodiments, the transmission trigger is controlled by waitingfor an amount of service usage, such as waiting until a certain amountof data traffic has passed, which reduces the control planecommunication channel traffic usage to a fraction of the data planetraffic. For example, this approach preserves network capacity andreduces service cost even in traffic scenarios in which data traffic islight.

In some embodiments, the transmission trigger is based on waiting for anamount of service usage, and also including a minimum transmission ratethat triggers a transmission according to one or more of the followingparameters: a maximum time between transmissions clock to keep theservice processor 115 in communication with the service controller 122when little or no service usage is occurring, a polling request of somekind from the service controller 122, a response to a service controllerheartbeat, a transmission generated by a service verification errorevent, or a transmission generated by some other asynchronous event withtime critical service processor 115 (or service controller 122)messaging needs, such as a transaction or service billing event or auser request. For example, service control plane traffic down is reducedto a relatively inexpensive and capacity conserving trickle when device100 data traffic is not significant. At the same time, this approachalso provides an effective flow of real time or near real-time servicecontrol plane traffic that is both cost and capacity efficient, becausethe service control plane traffic is a relatively small percentage ofthe data plane traffic when data plane traffic usage is heavy. Forexample, when data plane traffic usage is heavy is generally the timewhen close monitoring of service policy implementation verification orcompromise prevention can be particularly important and by keeping thecontrol plane overhead to a fraction of data plane traffic closemonitoring and control of services are maintained at a reasonable costin terms of percentage of both bandwidth used and network capacity. Insome embodiments, the service usage or service activity trigger occursbased on some other measure than traffic usage, such as a number ofmessages transacted, one or more billing events, number of filesdownloaded, number of applications run or time that an application hasbeen running, usage of one or more specified applications, GPScoordinate changes, roaming event, an event related to another networkconnection to the device and/or other service related measures.

In some embodiments, the service control device link 1691 provides forsecuring, signing, encrypting or otherwise protecting communicationsbefore sending. For example, the service control device link 1691 cansend to the transport layer or directly to the link layer fortransmission. In some embodiments, the communications are furthersecured with transport layer encryption, such as TCP TLS (TransportControl Protocol Transport Layer Security) or another secure transportlayer protocol. In some embodiments, communications are encrypted at thelink layer, such as IPSEC (Internet Protocol Security), various VPN(Virtual Private Network) services, other forms of IP layer encryptionand/or another link layer encryption technique.

In some embodiments, the service control link 1691 includes the abovediscussed agent heartbeat function in which the agents provide certainrequired reports to the service controller 122 for the purpose ofservice policy implementation verification (e.g., verification relatedreports on certain aspects of the service processor 115) or for otherpurposes. For example, such agent heartbeat messages can be in theopen/clear (unencrypted) or encrypted, signed and/or otherwise secured.In some embodiments, these messages include one or more of the belowdescribed types of messages: an agent information message, an agentcheck-in message and/or agent cross check message.

In some embodiments, an agent information message is included in theagent heartbeat service policy implementation verification message,which includes, for example, any information the agent needs tocommunicate to the service controller 122 as part of the operation ofthe service policy implementation system. For example, an agent responseto a service controller challenge, as described below, can be includedin the agent heartbeat service policy implementation verificationmessage.

In some embodiments, an agent check-in message is included in an agentheartbeat service policy implementation verification message, whichincludes, for example, a transmission of a unique agent identifier,secure unique identifier, and/or hashed encrypted and signed messagebeginning with some shared secret or state variable for the hash. Forexample, an agent self-check can be included in the agent heartbeatservice policy implementation verification message, which includesreporting on agent configuration, agent operation, agent code status,agent communication log, agent error flags, and/or other agentassociated information potentially hashed, encrypted, signed orotherwise secured in the message (e.g., using a shared secret unique tothat agent).

In some embodiments, an agent cross-check message is included in theagent heartbeat service policy implementation verification message,which includes, for example, reports on the status, configuration,operation observations, communication log or other aspects of anotheragent. For example, agent environment reports can be included in theagent heartbeat service policy implementation verification message,which includes, for example, reports on certain aspects of the serviceprocessor 115 operating environment, such as software presence (e.g.,installation status of certain operating system and/or applicationsoftware and/or components thereof), observed communication with agentsor communication attempts, memory accesses or access attempts, networkaccesses or access attempts, software downloads or attempted downloads,software removal or download blocking, service policy implementationverification or compromise event error conditions with respect to theoperating environment for the service processor 115, and/or othermessages regarding the verification or possibility of compromiseassociated with the service processor 115 operating environment oragents.

In some embodiments, the agent heartbeat function also provides regularupdates for information important to user service notification services.For example, the network based elements can provide regularsynchronization updates for the device based service usage or serviceactivity counters in which service usage or service activity measuresavailable from one or more network service history elements istransmitted to the device 100. This allows the service usage countererrors between the device service counter and the counters used forcentral billing to be minimized. A common service usage or serviceactivity measure is total traffic usage measured to date within a timeframe over which a service limit is applicable. Other service usage orservice activity measures can also be tracked and reconciled in asimilar manner.

In some embodiments for the heartbeat function, the service controller122 verifies that the scheduled agent reports are being received andthat the reports are within expected parameters. In some embodiments,the access control integrity server 1654 issues signedchallenge/response sequences to the policy implementation agent 1690.For example, the challenges can be asynchronous, issued when an event orerror condition occurs, issued on a schedule or issued when a certainamount of data has passed. This approach, for example, provides a secondlayer of service policy implementation verification that strengthens theservice usage or service activity measurement verification. For example,a challenge/response can be sent over the heartbeat link for the purposeof verifying device agent integrity. Various challenge/response relatedverification embodiments are described below.

In some embodiments, the challenge/response heartbeat message caninclude sending any kind of command or query, secure or transmitted inthe open, receiving a response from the agent and then evaluating theresponse to determine if the response is within a range of parametersexpected for a correctly configured agent, an agent that is operatingproperly, an agent that is not partially compromised or an agent that isnot entirely compromised. In some embodiments, the agent is onlyrequired to respond with a simple acknowledgement of the challenge. Insome embodiments, the agent is required to respond with a message orpiece of information that is known by the agent. In some embodiments,the agent is required to respond with a message or piece of informationthat is difficult for the agent to respond correctly with if it were tobe partially or entirely compromised. In some embodiments, the agent isrequired to respond back with information regarding the operation orconfiguration of the agent that is difficult for the agent to respondproperly with if the agent is not properly configured, not operatingproperly, is partially compromised or is entirely compromised. In someembodiments, the first agent is required to respond back withinformation regarding the operation, configuration, status or behaviorof a second agent that is difficult for the first or second agent torespond properly with if the first or second agent is not properlyconfigured, not operating properly, is partially compromised or isentirely compromised. In some embodiments, the agent is required torespond with a response that includes a shared secret. In someembodiments, the agent is required to respond with information regardingthe presence, configuration, operating characteristics or otherinformation regarding other programs in the operating environment of theagent. In some embodiments, the agent is required to respond with hashedinformation to be portions of code or a code sample (e.g., the codeportion or code sample can be specified by the service controller 122).

In some embodiments, the information the agent responds with is aresponse to a signed or encrypted message from the service controller122 in which the agent must know how to decode the encrypted controllermessage in order to respond correctly or it would be difficult for theagent to respond properly if the agent is not configured properly, isnot operating within appropriate limits, is partially compromised or isentirely compromised. In some embodiments, the agent signs or encryptsinformation in such a manner that it is difficult to respond correctlywhen the message is decoded by the service controller 122 unless theagent is configured properly, is operating within appropriate limits, isnot partially compromised and is not entirely compromised. In someembodiments, the agent is required to respond with a signed or encryptedhash of information that is difficult for the agent to generate unlessthe agent is configured properly, is operating within appropriatelimits, is not partially compromised and is not entirely compromised.For example, the hashed information can be local device configurationinformation, portions of code or all of the code, and/or the codeportion to be used in the response can be specified by the servicecontroller. In another example, the hashed information the agentresponds with can include a shared secret, and/or the hashed informationcan be information regarding the presence, configuration, operatingcharacteristics or other information regarding other programs in theoperating environment of the agent.

Accordingly, as described above, the agent heartbeat function providesan important and efficient system in some embodiments for verifying theservice policy implementation or protecting against compromise events.For example, there are many other functions the agent heartbeat servicecan perform and some are described herein while others will be apparentto one of ordinary skill in the art given the principles, designbackground and various embodiments provided herein.

In some embodiments, the service control device link 1691 facilitatesanother important function, which is the download of new serviceprocessor software elements, revisions of service processor softwareelements, and/or dynamic refreshes of service processor softwareelements. There are many embodiments for such operations. In someembodiments, the software is received as a single file over the servicecontrol device link 1691. For example, the file can have encryption orsigned encryption beyond any provided by the communication link protocolitself. In some embodiments, the software files are segmented intosmaller packets that are communicated in multiple messages sent over theservice control device link 1691. In some embodiments, once the file(s)are received, or the segmented portions of the file(s) are received,they are communicated to a service downloader 1663 for file aggregationand installation, which, in some embodiments, is performed after furthermeasures to verify the service processor software are completed. In someembodiments, the files are sent using other delivery means, such adirect TCP socket connection to the service downloader 1663 or someother software installer, which can also involve secure transport andadditional levels of encryption.

As shown in FIG. 16, an agent communication bus 1630 represents afunctional description for providing communication for the variousservice processor 115 agents and functions. In some embodiments, asrepresented in the functional diagram illustrated in FIG. 16, thearchitecture of the bus is generally multipoint to multipoint so thatany agent can communicate with any other agent, the service controlleror in some cases other components of the device, such user interface1697 and/or modem components. As described below, the architecture canalso be point to point for certain agents or communication transactions,or point to multipoint within the agent framework so that all agentcommunication can be concentrated, or secured, or controlled, orrestricted, or logged or reported. In some embodiments, the agentcommunication bus is secured, signed, encrypted, hidden, partitionedand/or otherwise protected from unauthorized monitoring or usage.

In some embodiments, as described below, there are multiple layers ofsecurity applied to the agent communication bus 1630 communicationprotocols, such as including one or more of the following: point topoint message exchange encryption using one or more keys that arepartially shared or shared within the service processor 115 agent groupand/or the service controller 122, point to point message exchange thatusing one or more keys that are private to the two endpoints of thecommunication, a bus-level message exchange encryption that can be inplace of or in addition to other encryption or security, or using one ormore keys that are partially shared or shared within the serviceprocessor 115 agent group and/or the service controller 122, a set ofsecure messages that can only be decoded or observed by the agents theyare intended for, a set of secure messages that allow communicationbetween certain agents or service processor functions and entitiesoutside of the service processor operating environment. In someembodiments, and as described herein, the service control device link1691 is assumed to be equivalent to an agent for communication purposes,and, in the case of the service control device link 1691, thecommunication is not restricted to the agent communication bus 1630 butalso extends to the service control communications link 1653. In someembodiments, the system has the capability to replace keys or signatureson occasion or on a regular basis to further secure against monitoring,eavesdropping or compromise of the agent communication system.

For example, various forms of message encryption and security frameworktechniques can be applied to encrypt and/or secure the agentcommunication bus 1630, including one or more of the following: agentbus encryption using shared key for all agents provided and updated bythe secure server; agent bus encryption using point to point keys inwhich the secure server informs the bus and agents of keys and updatesas appropriate; agent level encryption using agent to agent shared keysin which the secure server informs agents of the key and updates the keyas appropriate; agent level encryption using agent to agent point topoint key in which the secure server informs agent of the point to pointkeys that are required and updates the keys as appropriate; agent levelaccess authorization, which only allows access to the agents that are onthe secure authorization list and in which the list is provided by thesecure server and signatures are provided by the secure server; UImessages are only analyzed and passed, in which the UI cannot haveaccess to configuration information and cannot issue challenges; agentlevel heartbeat encryption, which can be point to point or shared keyfor that agent; control link level heartbeat encryption; TLS (TransportLayer Security) communication protocols; server level heartbeatencryption, which can be point to point or shared key for that secureserver; and/or the access control integrity agent 1694 or heartbeatfunction can become point to multipoint secure communications hubs.

In some embodiments of the agent communication bus 1630, the design ofthe agent communication bus depends on the nature of the designembodiments for the agents and/or other functions. For example, if theagents are implemented largely or entirely in software, then the agentcommunication bus can be implemented as an inter-process softwarecommunication bus. In some embodiments, such an inter-process softwarecommunication bus is a variant of D-bus (e.g., a message bus system forinter-process software communication that, for example, helpsapplications/agents to talk to one another), or another inter-processcommunication protocol or system, running a session bus in which allcommunications over the session bus can be secured, signed, encrypted orotherwise protected. For example, the session bus can be furtherprotected by storing all software (e.g., software components,applications and/or agents) in secure memory, storing all software inencrypted form in secure memory, and/or executing all software andcommunications within a secure execution environment, hardwareenvironment and/or protected memory space. In some embodiments, if theagents and other functions are designed with a mixture of software andhardware, or primarily with hardware, then the implementation of the busdesign will vary, and the principles and embodiments described hereinwill enable one of ordinary skill in the art to design the specifics ofthe agent communication bus 1630 to meet a particular set of product anddesired functional requirements.

As shown in FIG. 16, an access control integrity agent 1694 collectsdevice information on service policy, service usage or service activity,agent configuration and agent behavior. In some embodiments, the accesscontrol integrity agent 1694 also cross checks this information toidentify integrity breaches in the service policy implementation andcontrol system. In some embodiments, the access control integrity agent1694 also initiates action when a service policy violation or a systemintegrity breach is suspected. In some embodiments, the access controlintegrity agent 1694 also performs asynchronous or periodic agent checksto verify presence, configuration or proper operation of other agents.In some embodiments, the access control integrity agent 1694 alsoperforms challenge-response sequence verification of other agents.

In some embodiments, the access control integrity agent 1694 obtainsservice usage or service activity measures from a service monitor agent1696 and compares one or more first service usage measurement pointsagainst one or more second service usage measurement points to verifyservice policy implementation. For example, as shown in FIG. 21, if theservice usage at measurement point IV is inconsistent with measurementpoint III, which, for example, can indicate, for example, that anunauthorized or unmonitored usage of the access modem (e.g., modems2122, 2123, 2124, 2125 or 2141) is taking place. As another example, asalso shown in FIG. 21, if one or more aspects of upstream traffic usagemeasurement point II, which represents the upstream demand side ofpolicy implementation agent 1690, is inconsistent with upstream trafficmeasurement point III, which represents delivered traffic from thepolicy implementation agent 1690, then the policy implementation agent1690 may not be operating properly. As another example, as also shown inFIG. 21, if service measurement point III and IV indicate that firewallagent 1655 is passing traffic to URLs or IP addresses that are in theblocked policy settings, then a verification error condition can be setfor the access control policy. As another example, if the policycontroller reports traffic usage statistics that are inconsistent withtraffic usage policy settings, then a traffic usage policy verificationerror may have occurred. As another example, if the service usagecounter synchronization information received from the service controller122, the device service history 1618 and/or the central billing system1619, is compared to the service usage history reported by the servicemonitor agent and the two are found to be outside of acceptabletolerance limits for the comparison, then there may be a verificationerror in the service monitor service usage or service activityaccounting. There are numerous additional embodiments of suchcomparisons as described herein and others as will be readily apparentto one of ordinary skill in the art given the principles, designbackground and specific examples and various embodiments describedherein.

In some embodiments, device service policy implementations are verifiedby comparing various service usage measures used at the device againstexpected service usage or service activity behavior given the policies(e.g., one or more service policy settings, service profile or serviceprofile settings for network based access/services, and/or service planor service plan for network based access/services). For example,verification is performed based on a measure of total data passed at thedevice as compared to the service policy for total data usage. Forexample, verification is performed based on a measure of data passed ina period of time at the device as compared to the service policy fordata passed in such a period of time. For example, verification isperformed based on a monitoring of communications from the device basedon IP addresses as compared to the policy for permissible IP addresses.For example, verification is performed based on a measure of total datapassed from the device per IP address as compared to the policy fortotal data usage per IP address. Other examples include such actualversus policy comparisons based on other measures at/from/to the device,such as location, downloads, email accessed, URLs, and/or any otherdata, location, application, time or other criteria or any combinationof criteria that can be measured for comparing with various policysettings and/or restrictions.

In some embodiments, the access control integrity agent 1694 monitorsagent self-check reports to verify that agents are properly configured.In some embodiments, the access control integrity agent 1694 reports theagent self check reports to the service controller 122. In someembodiments, the access control integrity agent 1694 performs a role inservice usage test transmission, reception and/or monitoring, with theusage test being tailored to test monitoring or control aspects for anysubset of service activities. In some embodiments, the access controlintegrity agent 1694 performs a role in billing test event generationand/or monitoring. In some embodiments, the access control integrityagent 1694 checks and reports the result of service usage monitoringverification tests, service usage billing verification tests and/ortransaction billing verification tests.

In some embodiments, the access control integrity agent 1694 receivesagent access attempt reports to determine if unauthorized agent accessattempts are occurring. In some embodiments, the access controlintegrity agent 1694 acts as a central secure communications hub foragent to agent or service controller 122 to agent communication. Forexample, the access control integrity agent 1694 can be used so that noother software or function can access other agents or so that agentscannot access other agents except through the secure point to multipointcommunications hub. In some embodiments, this approach further enhancescompromise resistance for the agents. In some embodiments, some or allof the agent communications, including agent to agent or servicecontroller 122 to agent communications, and possibly includingunauthorized attempts to communication with agents, are monitored andlogged so that a trace log of some or all agent communications can bemaintained. For example, the agent communication trace log can besummarized and/or compressed for transmission efficiency or regularlyreported, such as through the heartbeat function, or the agentcommunication trace log can be reported only when the service controller122 requests the agent communication trace log or when there is averification error event. As similarly described above, the partitioningof agent functions and server functions is provided herein mainly to aidin disclosing various embodiments but those of ordinary skill in the artwill appreciate that other partitioning of agent functions and serverfunctions can be used based on different design choices. For example,the central agent communication hub function is performed in someembodiments by the access control integrity agent 1694, however, inother embodiments that function is performed by the service controldevice link 1691. For example, when the central agent communication hubfunction is located in the service control device link 1691, thenarchitecturally the device link can be a single point to multipointsecure communications hub for all agent to agent and service controller122 to agent communications. In some embodiments, this approach hascertain advantages from a service policy implementation verification orcompromise protection robustness perspective, or has certain advantagesfrom a communications protocol efficiency perspective, or simply can bemore efficient to implement. It should be noted that in otherembodiments described herein the agent to agent and agent to servicecontroller 122 communications can be multipoint to multipoint, with eachagent having the capability to communicate with other agents or theservice controller, this communication can be secure, signed orotherwise encrypted or protected in some embodiments and in theopen/clear in others. Also, as discussed in some embodiments, the agentscan maintain their own communications or attempted communications log,which can then be reported to the service controller 122. In someembodiments, the agents implement restrictions on which devicecomponents or agents the agents will conduct communications with so thatonly agents that need to communicate with one another can do so.

In some embodiments, the service control device link 1691 reviews localbilling event history and compares such history to billing event reportsto verify that a billing agent 1695 is functioning properly (e.g., hasnot been tampered with or compromised). In some embodiments, the servicecontrol device link 1691 cross-checks service usage or service activityagainst billing event reports from the billing agent 1695 to verify thatbilling events are properly billing for service usage or serviceactivity. In some embodiments, the service control device link 1691cross-checks transaction billing process or records against transactionbilling reports to ensure that transaction billing events are beingproperly reported by the billing agent 1695. In some embodiments, theservice control device link 1691 determines if one or more agents havebeen compromised, and if so, initiates a dynamic agent download processto replace any such potentially compromised agent.

In some embodiments, the access control integrity agent 1694 verifiesthat the service usage counter is reporting service usage or servicecost to the user within acceptable limits of accuracy when compared tothe service usage reports obtained from the service monitor agent 1696,the service controller 122, the device service history 1618 and/or thecentral billing system 1619. In some embodiments, the access controlintegrity agent 1694 checks to verify that user privacy filterpreferences are being properly implemented. In some embodiments, theaccess control integrity agent 1694 checks to verify that the user isproperly receiving UI warnings regarding service usage or roamingservice usage conditions.

In some embodiments, the access control integrity agent 1694 checks toverify that the device is not beginning service usage until it has beenauthenticated, authorized or granted access to the network. In someembodiments, access control integrity agent 1694 checks with the servicecontroller 122 or the billing system 1619 to verify that the user ordevice has a valid service standing and should be admitted to access onthe network.

In some embodiments, an Activation Tracking Service (ATS) is provided inwhich the service monitoring function (e.g., performed by the servicemonitor agent 1696 and/or some other agent/component or combinationsthereof on the device) is used in part to determine which accessnetworks are being connected to and to record and/or report thisinformation. In some embodiments, the ATS is only enabled if the deviceuser approves reporting of access networks connected to by the userdevice. In some embodiments, the ATS is protected from tampering. Forexample, the ATS can be hardened, that is, to be more tamper resistant,using a variety of techniques, including any of the following: the ATScan be located (e.g., stored) in secure memory and/or secure hardware;the ATS can be implemented in the system BIOS, the access modem and/oranother hard to access portion of the device; a second device agent canconfirm the presence of the ATS with a report to a network based server;the second agent or the network server can initiate a reinstall of theATS if it is missing or is found to be operating improperly; and/or theATS can be placed in a secure area of the OS so that it cannot beremoved or if removed must be replaced for proper device operation toresume. A variety of other tamper resistance techniques can also be usedto protect the ATS from tampering as similarly described herein withrespect to other device based functions/software components/agents.

In some embodiments, the access control integrity agent 1694 verifiesthat ATS software or hardware is present, properly configured oroperating properly. In some embodiments, the access control integrityagent 1694 reviews network connection or activity history and comparessuch to ATS reports to verify activation tracking service reports areoccurring properly. In some embodiments, the access control integrityagent 1694 replaces ATS software if it has been removed. In someembodiments, the access control integrity agent 1694 monitors access orcompromise of ATS software to determine if it may have been compromised.In some embodiments, the access control integrity agent 1694 reportsstatus of ATS functions.

In some embodiments, the access control integrity agent 1694 scans thelocal agent execution environment to determine if there are unauthorizedaccesses to service processor functions, settings or code. In someembodiments, the access control integrity agent 1694 monitors softwareloading activity, protected memory access or communication with serviceprocessor 115 agents to detect unauthorized changes to service processorsoftware or configuration. For example, the access control integrityagent 1694 can have a local database of potentially malicious elementsand compare entries in the database against the elements detectedlocally. As another example, the access control integrity agent 1694 cancommunicate a list of some or all of the elements detected locally tothe service controller 122 to augment or take the place of the databasecomparison function that may be performed locally. In some embodiments,the access control integrity agent 1694 detects new software downloads,installs or invocations and immediately issues an error flag report whenpotentially malicious software is downloaded, installed or invoked. Insome embodiments, the access control integrity agent 1694 scans thelocal software loading and invocation activity along with a log of othersoftware runtime events and regularly reports this trace so that when anerror or compromise event occurs the trace preceding the event can beanalyzed to determine the offending software or activity trace that tookplace to cause the compromise or error. Once the software or activitythat caused the compromise is known, it can be entered into a refreshedversion of the database that the device and other devices use to detectpotentially malicious pre-cursor conditions. Examples of such pre-cursorevents include software invocations, software downloads, attempts touninstall certain agent and/or application software/components or OScomponents, a sequence of memory I/O events, a sequence of softwareaccess events, a sequence of network address or URL communications ordownloads or a sequence of access modem I/O activity. In various otherembodiments of the access control integrity agent 1694, the agentperforms or (securely) communicates with other software/hardwaredevice/network components that perform other well known signature,behavior blocking and/or intrusion detection identification/detectionand/or blocking techniques based on the presence of potentially unwantedand/or potentially or known malicious software and/or intrusion attemptsby unauthorized software and/or unauthorized users, using, for example,real-time, on access, periodic, and/or on demand scanning.

In some embodiments, the access control integrity agent 1694 detects orblocks potentially compromising behavior of other softwareprograms/users attempting unauthorized behavior in the service processor115 operating environment. In some embodiments, the access controlintegrity agent 1694 detects software that is being loaded that has thesame or similar name, identification, memory location or function as oneor more of the service processor 115 agents. In some embodiments, theaccess control integrity agent 1694 blocks operation or loading of suchsoftware. In some embodiments, the access control integrity agent 1694detects or blocks unauthorized access of service processor 115 protectedmemory. In some embodiments, the access control integrity agent 1694verifies configuration and operation of secure service downloader 1663.In some embodiments, the access control integrity agent 1694 monitorsnetwork and I/O activity to detect potentially compromising events, suchas a program that is downloaded from known detrimental or potentiallysuspect IP addresses or URLs or a program that accesses certain IPaddresses or URLs. In some embodiments, the access control integrityagent 1694 scans of the service processor operating environment arerecorded and kept for a period of time, and if a service policyverification error occurs, then the scans immediately prior to the errorare analyzed or reported to the service controller 122 for analysis. Insome embodiments, such scans are regularly reported to the servicecontroller 122 without the presence of service policy verification errorconditions.

In some embodiments, the access control integrity agent 1694 requests adynamic agent download of certain critical service processor functions,including in some cases the access control integrity agent 1694 on aperiodic basis, or on a periodic basis when network access activity isnot required or minimal.

In some embodiments, the access control integrity agent 1694 determinesif a threshold has been surpassed for a max usage trigger for ambientand/or other services that should not be using significant amounts ofdata (e.g., based on the type of device and/or service profilesettings).

In some embodiments, the access control integrity agent 1694 determinesif verification errors exist in one or more of the verification processembodiments and, in some embodiments, reports errors immediately or inthe next agent heartbeat to the service controller 122. In someembodiments, any number of results from the above checks, monitoringactivities, reports or tests are reported to the service controller 122.

In some embodiments, a policy control agent 1692 receives policyinstructions from the service controller 122 and/or the user via thebilling agent 1695 and adapts device service policy settings (e.g.,instantaneous device service policy settings) in one or more of thefollowing agents/components: a policy implementation agent 1690, themodem firewall 1655 and/or an application interface agent 1693. As shownin FIG. 16, the modem firewall 1655 is in communication with a modemdriver 1640, which is in communication with the agent communication bus1630 and access network 1610. As shown with respect to access network1610, a central billing server 1619, an access network AAA server 1621and device server history 1618 are also provided. As shown, the Internet120 is accessible via the access network 1610 and firewall 124, fromwhich device 100 can then access various Internet services 1615.

In some embodiments, the policy control agent 1692 adapts low levelservice policy rules/settings to perform one or more of the followingobjectives: achieve higher level service usage or cost objectives,reduce network control channel capacity drain, reduce network controlplane server processing bandwidth, and/or provide a higher level of userprivacy or network neutrality while satisfying service usage or serviceactivity objectives. In some embodiments, the policy control agent 1692performs a policy control function to adapt instantaneous servicepolicies to achieve a service usage objective. In some embodiments, thepolicy control agent 1692 receives service usage information from theservice monitor agent 1696 to evaluate service usage history as comparedto service usage goals. In some embodiments, the policy control agent1692 uses service monitor 1696 service usage or service activity historyand various possible algorithm embodiments to create an estimate of thefuture projected service usage. In some embodiments, the policy controlagent 1692 uses a future projection of service usage to determine whatservice usage or service activity controls need to be changed tomaintain service usage goals. In some embodiments, the policy controlagent 1692 uses service usage history to perform a service usage orservice activity analysis to determine the distribution of service usageacross service usage elements within categories, such as usage byapplication, usage by URL, usage by address, usage by content type,usage by time of day, usage by access network, usage by location, and/orany other categories for classifying service usage. In some embodiments,the policy control agent 1692 uses the service usage distributionanalysis to determine which service usage elements or service activitiesare creating the largest service usage (e.g., if e-mail, socialnetworking, or multimedia/online video application categories arecreating the largest service usage).

In some embodiments, the policy control agent 1692 is instructed, forexample, by the user, through billing agent 1695 to perform a servicecontrol algorithm, such as traffic shaping or download management, tomanage service usage or service activities to assist the user incontrolling service costs. As a basic example of such a traffic shapingalgorithm, the traffic shaping algorithm can simply reduce traffic speedfor all applications and traffic types successively until the serviceusage projections are within service usage limits for the presentservice billing period. To illustrate an algorithm that is moresophisticated and provides the advantage of leaving many service usageelements or service activities unaffected while only controlling downusage on the most aggressive service usage elements or serviceactivities, the traffic shaping algorithm can identify the highesttraffic usage applications and/or websites and successively reducetraffic speed just for the highest usage applications and/or websitesuntil the service usage projections are within service usage limits forthe present service billing period. These examples thereby reducenetwork traffic for the user in accordance with the user's service usageobjectives while maintaining overall satisfactory service usageexperience for the user in a manner that satisfies various netneutrality requirements (e.g., the traffic throttling of certainapplications/websites based on user input in which categories based onservice usage history are selected by the user, for example, a certainapplication may be using 90% of the aggregate traffic usage). Forexample, adaptive throttling algorithms can be used to throttleapplication traffic that the user requests throttling, such asrecursively throttling of the specified application traffic (e.g., todenigrate the traffic usage associated with that application and therebyreduce overall service data usage).

In some embodiments, the policy control agent 1692 adjusts servicepolicy based on time of day. In some embodiments, the policy controlagent 1692 obtains a measure of network availability and adjusts trafficshaping policy settings based on available network capacity. In someembodiments, the policy control agent 1692 automatically and dynamicallyadjusts service policy based on one or more other service policysettings, the service profile and/or the service plan associated withthe device and/or user of the device.

In some embodiments, various lower level service policy implementationembodiments are combined with a higher level set of service policysupervision functions to provide device assisted verifiable networkaccess control, authentication and authorization services.

In some embodiments, device based access control services are extendedand combined with other policy design techniques to create a simplifieddevice activation process and connected user experience referred toherein as ambient activation. In some embodiments, ambient accessgenerally refers to an initial service access in which such serviceaccess is in some manner limited, such as where service options aresignificantly limited (e.g., low bandwidth network browsing and/oraccess to a specific transactional service), limited bandwidth, limitedduration access before which a service plan must be purchased tomaintain service or have service suspended/disabled or throttled orotherwise limited/reduced/downgraded, and/or any other time based,quality based, scope of service limited initial access for the networkenabled device. In some embodiments, ambient activation is provided bysetting access control to a fixed destination (e.g., providing access toa portal, such as a web page (e.g., for a hotspot) or WAP (WirelessApplication Protocol) page, that provides the user with service planoptions for obtaining a service plan for the user desired access, suchas the service plan options for data usage, service types, time periodfor access (e.g., a day pass, a week pass or some other duration), andcosts of service plan(s)). In some embodiments, service data usage ofthe ambient activated device is verified using IPDRs (e.g., using thedevice ID/device number for the device 101 to determine if the devicehas been used in a manner that is out of plan for the service planassociated with the device 101, such as based on the amount of datausage exceeding the service plan's service data usage limits, out ofplan/unauthorized access to certain websites, and/or out ofplan/unauthorized transactions). In some embodiments, service data usageof the ambient activated device is verified by setting a maximum datarate in the policy control agent 1692 and if/when it is determined thatthe device is exceeding a specified data rate/data usage, then theservice data usage is throttled accordingly. In some embodiments,various other verification approaches are used for ambient activationpurposes.

In some embodiments, the policy control agent 1692 (and/or anotheragent/component of the service processor 115 and/or service controller122) performs a service control algorithm to assist in managing overallnetwork capacity or application QoS (Quality of Service). In someembodiments, the policy control agent 1692 (and/or anotheragent/component of the service processor 115) performs an access networkselection algorithm to determine which access network to connect tobased on connection options and determined strengths of availablewireless networks, network preference or security settings, serviceusage cost based network preferences, and/or any other criteria.

Accordingly, as described herein with respect to various embodiments,service usage or service activities can be measured by various agents atvarious different measurement points, which provides for a more robustverification and integrity of device based services communication. Forexample, it is much less likely and more difficult to compromise and/orspoof multiple agents. As described herein, various verification andintegrity checks are performed, including, for example, network basedservice usage measurement (e.g., using IPDRs); heartbeat monitoring;agent based heartbeat (e.g., challenge/response queries); agentoperating environment protection; monitoring agent communications; agentcross-checks; comparing device based and network based measures (e.g.,service usage measures); dynamic software/agent download; and/or anycombination of these and various other verification/integrity checktechniques described herein and/or apparent from the various embodimentsdescribed herein.

In some embodiments, the device 100 is capable of connecting to morethan one network and device service policies are potentially changedbased on which network the device is connected to at the time. In someembodiments, the network control plane servers detect a networkconnection change and initiate the service policy implementationestablished for the second network. In some embodiments, the devicebased adaptive policy control agent, as described herein (e.g., policycontrol agent 1692), detects network connection changes and implementsthe service policies established for the second network.

In some embodiments, when more than one access network is available, thenetwork is chosen based on which network is most preferred according toa network preference list or according to which network that optimizes anetwork cost function. For example, the network preference list can bepre-established by the service provide and/or the user and/or latermodified/adjusted by either the service provider and/or the user. Forexample, the cost function can be based on determining a minimum servicecost, maximum network performance, whether or not the user or device hasaccess to the network, maximizing service provider connection benefit,reducing connections to alternative paid service providers, and/or anyother cost related criteria for network selection purposes.

In some embodiments, the device 100 detects when one or more preferrednetworks are not available, implements a network selection function orintercepts other network selection functions, and offers a connection tothe available service network that is highest on a preference list. Forexample, the preference list can be set by the service provider, theuser and/or the service subscriber. In some embodiments, a notificationis provided to the device/user when the device is not connected to anetwork (e.g., indicating in a pop-up/bubble or other UI based display anotification, such as “You are not connected to the network. Click hereto learn more, get free trial, use a session, sign-up for service”). Insome embodiments, the notification content can be determined based onusage service patterns, locally stored and/or programmable logic on thedevice and/or a server (e.g., device reports that user is not connectedand WWAN is available). Decisions on what bubble to present when may bein pre-stored logic on device.

In some embodiments, service policies are automatically adapted based onthe network to which device 100 is connected. For example, the devicecan be a cellular communication based device connected to a macrocell, amicrocell, a picocell, or a femtocell (e.g., femto cells generallyprovide a low power, small area cellular network used, for example, inhomes or offices, which, for example, can be used as an alternative toWi-Fi access). In some embodiments, service monitoring agent 1696 and/orbilling agent 1695 modify service usage counting and/or billing based onwhether the device is connected to a macrocell, microcell, picocell orfemtocell. In some embodiments, the device recognizes which type ofnetwork it is currently connecting to (e.g., looking up in a local ornetwork table for the current base station connected to, and/or theinformation is broadcast to the device upon the connection with the basestation), that is, whether it is a macrocell, microcell, picocell orfemtocell. In other embodiments, the device does not recognize whichtype of network it is currently connected to, but reports its currentbase station, and the network uses a network lookup function todetermine which type of network it is connected to. In some embodiments,the device adjusts the billing based on the type of network it isconnected to, or in other embodiments, the device calculates an offsetto such billing based on the type of network it is connected to, and/orin other embodiments, the device records such service usage associatedwith the type of network it is connected to and the network billing canadjust the billing accordingly. For example, the billing can be lowerfor service data usage over a femtocell versus a macrocell. In someembodiments, service policies are adjusted based on the type of networkthat the device is connected, such as billing, user notification, datausage/bandwidth, throttling, time of day, who owns the cellular networkconnection (e.g., user's home femtocell, or user's work femtocell, or acommercial business's femtocell like a coffee shop or any other commonarea like an airport) and/or any other service policy can be differentfor a femtocell connection (or for any other type of connection, such asa macrocell, microcell, or picocell). In some embodiments, the localservice usage counter is adjusted based on the type of network (and/orbased on the time of day of such service activity) that the device isconnected, such as billing, user notification, data usage/bandwidth,and/or any other service policy can be different for a femtocellconnection (or for any other type of connection, such as a macrocell,microcell, or picocell). In some embodiments, the service policiesand/or billing policies are adjusted based on network congestion.

In some embodiments, if adaptive service policy control is not required,then the policy control agent 1692 can simply pass instantaneous servicepolicy settings directly to the agents responsible for implementinginstantaneous service policies.

In some embodiments, a policy implementation agent 1690 implementstraffic shaping and QoS policy rules for the device 100. In someembodiments, the policy implementation agent 1690 provides a firewallfunction. In some embodiments, the policy implementation agent 1690performs traffic inspection and characterization. In some embodiments,packet inspection is aided by literal or virtual application layertagging while in other embodiments packet inspection is performedentirely in/by the policy implementation agent 1690. In someembodiments, the policy implementation agent 1690 accepts service policyimplementation settings from the policy control agent 1692 or directlyfrom the service controller 122. More detail on specific embodiments forthe policy implementation agent 1690 is provided below with respect tothe figures associated with communication stack and communicationprotocol flow.

In some embodiments, the burst size, buffer delay, acknowledgement delayand drop rate used in upstream and downstream traffic shaping areoptimized with the goal of reducing access network traffic overhead, andexcess capacity usage that can result from mismatches in traffictransmission parameters with the access network MAC and PHY or fromexcess network level packet delivery protocol re-transmissions. In someembodiments, the application interface agent 1693 is used to literallytag or virtually tag application layer traffic so that the policyimplementation agent(s) 1690 has the necessary information to implementselected traffic shaping solutions. As shown in FIG. 16, the applicationinterface agent 1693 is in communication with various applications,including a TCP application 1604, an IP application 1605, and a voiceapplication 1602.

In some embodiments, downstream literal or virtual application taggingare delayed until a traffic flow passes through the service policyimplementation functions and to the application interface function wherethe service flow is then identified and associated with the underlyingtraffic and application parameters, and the literal or virtual tag isthen communicated to the first policy implementation function or servicemonitoring function in the downstream traffic processing stack. In someembodiments, prior to being associated with a literal or virtual tag,the traffic flow is allowed to pass with no traffic shaping, and oncethe traffic flow is identified and tagged, the appropriate trafficshaping is applied. In some embodiments, a set of traffic shaping policyparameters are applied to the unidentified traffic flow before the flowis identified, and then the traffic shaping policy for the flow isupdated when the flow is tagged. In some embodiments, the traffic flowcan be blocked at the application interface agent even before the tag ispassed to the policy implementation functions if it is found to beassociated with traffic parameters that are blocked by policy oncepacket processing, framing and encryption are removed.

In some embodiments, a service monitor agent 1696 records and reportsdevice service usage or service activities of device 100. In someembodiments, service usage history is verified by a number of techniquesincluding verifying against network based service usage history (e.g.,device service history 1618) and the various service policyimplementation techniques as described herein.

In some embodiments, the service monitor agent 1696 includes thecapability to filter service usage history reporting with the decisionon which aspects of service history to report being determined bypolicies including possibly privacy policies defined by the device useror control plane servers in the network. In some embodiments, theservice monitor agent 1696 monitors and possibly records or reportsCustomer Resource Management (CRM) information such as websites visited,time spent per website, interest indications based on website viewing,advertisements served to the device, advertisements opened by the user,location of the user, searches conducted by the user, application usageprofile, device user interface usage history, electronic commercetransactions, music or video files played, applications on device,and/or when the user is actively working or playing or inactive. In someembodiments, to protect the privacy of this user CRM information, theuser is provided with options on how much of the information to shareand the user's response to the options are recorded and used todetermine the filtering policy for how much of the CRM data to report(e.g., CRM filter level options selected by the user via the device UIand/or via various service plan or service profile or service policyoptions) and how much to suppress or to not even monitor/record/store inthe first place. In some embodiments, to protect the privacy of thisuser's GPS/location tracking related information, the user is providedwith options on how much of the information to share and the user'sresponse to the options are recorded and used to determine the filteringpolicy for how much of the GPS/location tracking related data to report(e.g., GPS/location tracking filter level options) and how much tosuppress or to not even monitor/record/store in the first place. In someembodiments, the service processor 115 allows the user to providefeedback on the user's preferences, such as for privacy/CRM data toreport. In some embodiments, the user can also specify theirpreference(s) for notification (e.g., related to service usage/cost,traffic reporting and other service usage/monitored information) and/orservice controls. In some embodiments, the service monitor agent 1696observes and possibly records or reports service usage categorized bynetwork possibly including roaming networks, paid service networks orfree service networks. In some embodiments, the service monitor agent1696 observes and possibly records or reports service usage categorizedby sub-accounts for various types of traffic or various types ofnetwork.

For example, service monitor reports can be provided to the servicecontroller 122. Service is monitored through various embodiments thatcan involve service usage logging or traffic inspection and usagelogging at the application level, various levels in the networkingcommunication stack or the access modem. Some embodiments involvemultiple levels of service or traffic measurement at various levels inthe communications stack as described further below.

In some embodiments, service or traffic monitoring includes monitoringone or more of the following: traffic associated with one or more users;traffic downstream and/or upstream data rate; total traffic receivedand/or transmitted over a period of time; traffic transmitted and/orreceived by IP addresses, domain names, URLs or other network addressidentifiers; traffic transmitted and/or received by email downloads oruploads; traffic transmitted and/or received by an application; traffictransmitted and/or received by network file transfers; traffictransmitted and/or received by file download or upload content types;traffic transmitted and/or received by mobile commerce transactions;traffic transmitted and/or received by one or more time periods; traffictransmitted and/or received by differing levels of network activity andnetwork capacity availability; traffic transmitted and/or received byone or more delivered levels of quality of service; traffic transmittedand/or received by software downloads; traffic transmitted and/orreceived by application downloads; traffic transmitted and/or receivedby one or more activities associated with the service control plane linkor other network related functions, or traffic that may not directlyresult in service usage or service activity that the user values ordesires; traffic transmitted and/or received to support one or moreservice provider third party service partner offerings; software usagehistory; application usage history; device discovery history for UIcomponents, applications, settings, tutorials; ads served history; adsvisited history; and/or device location history.

In some embodiments, some or all of the service usage monitoring occursat the application layer. In some embodiments, the service monitor agent1696 implements traffic inspection points between the applications andthe networking stack application interface, such as the sockets API. Inother embodiments, the application interface agent 1693 performs trafficinspection and reports the results to the service monitor agent 1696.Traffic inspection can be accomplished in several ways, including, forexample, implementing a T-buffer at each socket connection and feedingthe side traffic into a traffic flow analyzer, which in combination witha mapping of application to socket provides much of the informationlisted above. In cases in which it is necessary to obtain trafficinformation from the application itself, some embodiments call for theapplication to be adapted to provide the information to either theapplication interface agent 1693 or the service monitor agent 1696. Asan example, the application interface agent 1693 or the service monitoragent 1696 can monitor and decode advertisements downloaded via HTTP,but if the browser and HTTP server employ security above the socketsprotocol stack layer then the application interface agent cancommunicate with the browser via a java applet or some otherinter-process communication method. In some embodiments, the servicemonitor agent 1696, the billing agent 1695 and/or the policy controlagent 1692 (or some other software or hardware function on the device)can monitor and/or control (e.g., allow, block and/or replace)advertisement traffic flow into the device. In some embodiments, themonitoring and control of advertisement traffic flow into the device isalso used for bill by account purposes (e.g., charges, such as servicecharges, billed to the advertiser, sponsor, and/or service ortransactional service provider).

In some embodiments, some or all of the service usage monitoring occursbelow the application interface for the networking stack. In this case,some portion of the information listed above may not always be availabledue to encryption applied at the higher layers and/or the computationalcosts associated with performing deep packet inspection on mobiledevices.

In some embodiments, the service monitor agent 1696 is also monitors theoperating software install or loading systems, and/or otherwise monitorssoftware installs or loads and/or software uninstalls/deinstallations.

Some of the information above may be considered by some users, advocacygroups or agencies as customer sensitive personal information. Simplysending the above information to the network for unspecified purposesmay not, therefore, be acceptable for some service providers. However,if the user provides specific approval (e.g., informed consent) for thedevice, network or service provider to use some or all of theinformation that may be sensitive for specified purposes, then the usercan control the level of information that is used and the purpose theinformation is used for. Accordingly, various embodiments describedherein provide the user with control of what information is used and thepurposes it is used for thereby allowing the user adequate control ofany such sensitive information. In some embodiments, information that isthought to perhaps be sensitive and is reported to the network mustfirst receive user approval for the reporting. Some basic information isgenerally not considered sensitive and is necessary for certain basicservice provider needs. For example, total data transmitted and/orreceived, traffic downstream and/or upstream speed, overall trafficusage by time of day are generally not considered private from theservice provider's perspective and are necessary in many basic servicepolicy implementations. As additional examples, perhaps other serviceusage history, such as total traffic email downloads and uploads but notthe type of files or any specifics about the email traffic, the totalweb browsing traffic but nothing specific about the sites visited orcontent viewed, total file transfer traffic but not the type of filestransferred or the addresses involved in the transfer, and otherexamples may not be viewed as private and, in some embodiments, providevaluable information for the service provider to manage services.Conversely, information such as websites visited, content viewed, mobilecommerce transactions completed, advertisements visited, GPS locationhistory and other service usage history the service monitor is capableof recording may be sensitive or private for some users and wouldthereby benefit from the various embodiments that provide enhanced usercontrol of the reporting of such potentially sensitive or private data.It should also be appreciated that there is an inherent advantage toimplementing traffic monitoring, traffic, service monitoring or servicecontrol on a device, because it is not necessary to report sensitiveinformation to the network to accomplish many of these service policyimplementation objectives.

In some embodiments, the service monitor agent 1696 assists in virtualapplication tagging of traffic flows through the networking stack policyimplementation by tracking the virtually tagged packets through thestack processing and communicating the flow tags to the service policyimplementation agent(s) 1690. In some embodiments, the service monitoragent 1696 maintains a history and provides reports or summary reportsof which networks in addition to the networks controlled by the servicecontroller 122 to which the device has connected. In some embodiments,this network activity summary includes a summary of the networksaccessed, activity versus time per connection, and/or traffic versustime per connection. In some embodiments, the traffic reports that go tothe network, possibly to service controller 122, billing system 1619and/or device service history 1618, are first filtered according torules defined by user preference selection at the time of serviceactivation (e.g., service plan/service plan option selection), time offirst device use, at a time the user selected the option on the serviceUI or at a time the user chose to change the option on the service UI orsome other time/mechanism allowing for user preference selection.

In some embodiments, the service monitor agent 1696 monitors applicationusage (e.g., which application the user executes on the device 101, suchas e-mail applications, web browsing applications and/or media contentstreaming applications). In some embodiments, the service monitor agent1696 monitors multimedia file usage (e.g., based on multimedia file typeand/or based on specific multimedia files, such as specific moviesand/or songs). In some embodiments, the service monitor agent 1696monitors the device user interface, application, and content discoveryhistory (e.g., monitoring which applications/content the user accessesfrom the device, including monitoring the pattern by which the useraccesses such applications/content, such as how the user navigates theuser interface on the device to access such applications/content andmaintaining such patterns and history, such as which icons the useraccess on a home page, secondary or other portion/mechanism on thedevice for accessing various applications/content). In some embodiments,the service monitor agent 1696 monitors advertisements provided to theuser on the device 101. In some embodiments, the service monitor agent1696 monitors advertisements viewed (e.g., accessed, such as by clickingon a web advertisement) by the user on the device 101. In someembodiments, the service monitor agent 1696 monitors GPS/locationinformation for the device 101. As will be appreciated by those ofordinary skill in the art, the service monitor agent 1696 can monitor awide variety of activities performed by the device/user of the deviceand/or based on other information related to the device 101 such asGPS/location information. As described herein, in some embodiments, theuser of the device 101 can also specify which activities that the userauthorizes for such monitoring (e.g., the user may prefer to not allowfor such GPS/location monitoring).

In some embodiments, the application interface agent 1693 provides aninterface for device application programs. In some embodiments, theapplication interface agent 1693 identifies application level traffic,reports virtual service identification tags or appends literal serviceidentification tags to assist service policy implementation, such asaccess control, traffic shaping QoS control, service type dependentbilling or other service control or implementation functions. In someembodiments, the application interface agent 1693 assists withapplication layer service usage monitoring by, for example, passivelyinspecting and logging traffic or service characteristics at a point inthe software stack between the applications and the standard networkingstack application interface, such as the sockets API. In someembodiments, the application interface agent 1693 intercepts trafficbetween the applications and the standard network stack interface API inorder to more deeply inspect the traffic, modify the traffic or shapethe traffic (e.g., thereby not requiring any modification of the devicenetworking/communication stack of the device OS). In some embodiments,the application interface agent 1693 implements certain aspects ofservice policies, such as application level access control, applicationassociated billing, application layer service monitoring or reporting,application layer based traffic shaping, service type dependent billing,or other service control or implementation functions.

In some embodiments, application layer based traffic monitoring andshaping can be performed as described below. The traffic from eachapplication can be divided into one or more traffic flows that each flowthrough a traffic queue, with each queue being associated with one ormore additional classifications for that application (e.g., theapplication can be a browser that is associated with multiple queuesrepresenting different destinations or groups of destinations it isconnected to, with each destination or group of destinations havingpotentially different access control or traffic control policies, or theapplication can be associated with different content types or groups ofcontent types with each content type having different queues, theapplication might be an email program with email text traffic going toone queue and downloads going to another with different policies foreach). In some embodiments, queues are formed for all applications orgroups of applications that are associated with one or more trafficparameters such as destination, content type, time of day or groups ofapplications can be similarly assigned to different queues. Thefunctions performed by the application layer queues can be similar tothe functions described for the policy implementation agent, such aspass, block, buffer, delay, burst in order to control the traffic ornetwork access associated with the queue. The drop function can also beimplemented, such as for application layer protocols that includereliable transmission methods, but if the application layer protocoldoes not involve reliable retransmission of lost information this canresult in lost data or unreliable communication which may be acceptablein some cases. The manner in which the queues are controlled can beconstructed to result in a similar approach for controlling services orimplementing service activity control similar to the other embodimentsdescribed herein, including, for example, the policy control agent 1692implementing an higher layer of service control to achieve a higherlevel objective as discussed herein.

In some embodiments, the application interface agent 1693 interacts withapplication programs to arrange application settings to aid inimplementing application level service policy implementation or billing,such as email file transfer options, peer to peer networking filetransfer options, media content resolution or compression settingsand/or inserting or modifying browser headers. In some embodiments, theapplication interface agent 1693 intercepts certain application trafficto modify traffic application layer parameters, such as email filetransfer options or browser headers. In some embodiments, theapplication interface agent 1693 transmits or receives a service usagetest element to aid in verifying service policy implementation, servicemonitoring or service billing. In some embodiments, the applicationinterface agent 1693 performs a transaction billing intercept functionto aid the billing agent 1695 in transaction billing. In someembodiments, the application interface agent 1693 transmits or receivesa billing test element to aid in verifying transaction billing orservice billing.

In some embodiments, a modem firewall 1655 blocks or passes trafficbased on service policies and traffic attributes. In some embodiments,the modem firewall 1655 assists in virtual or literal upstream trafficflow tagging. Although not shown in FIG. 16, in some embodiments, themodem firewall 1655 is located on either side of the modem bus and insome embodiments it is advantageous to locate it on the modem itself.

In some embodiments, the billing agent 1695 detects and reports servicebilling events. In some embodiments, the billing agent 1695 plays a keyrole in transaction billing. In some embodiments, the billing agent 1695performs one or more of the following functions: provides the user withservice plan options, accepts service plan selections, provides optionson service usage notification policies, accepts user preferencespecifications on service usage notification policies, providesnotification on service usage levels, provides alerts when service usagethreatens to go over plan limits or to generate excess cost, providesoptions on service usage control policy, accepts choices on serviceusage control policy, informs policy control agent 1692 of userpreference on service usage control policy, provides billing transactionoptions and/or accepts billing transaction choices. In some embodiments,the billing agent 1695 interacts with transaction servers (e.g., opencontent transaction partner sites 134) to conduct ecommerce transactionswith central billing 1619.

In some embodiments, service processor 115 includes one or more serviceusage or service activity counters. For example, the service monitoragent 1696, billing agent 1695 or a combination of these agents and/orother agents/components of service processor 115 can include such alocal service usage counter(s) for the device 101. In some embodiments,a service usage counter monitors service usage including data usageto/from the device 101 with the access network 1610. In someembodiments, the service usage counter periodically, in response to auser request, in response to a service processor 115 agent's request(e.g., the billing agent 1695, the policy control agent 1692, or anotheragent of service processor 115), in response to the service controller122, and/or in response to the central billing 1619 (e.g., for billingpurposes and/or for storing in the device service history 1618),provides a service usage report, including monitored service usage forthe device 101. In some embodiments, the service usage counterperiodically, or in response to a request, synchronizes the serviceusage counter on the device 101 with a network (and/or billing) serviceusage counter, such as that maintained potentially at central billing1619. In some embodiments, service processor 115 utilizes the serviceusage counter to provide a service usage projection. In someembodiments, service processor 115 utilizes the service usage counter toprovide a service usage cost estimate. In some embodiments, serviceusage projections from policy control agent 1692 are used to estimatethe projected future service usage if user service usage behaviorremains consistent. In some embodiments, service processor 115 utilizesthe service usage counter to provide a cost of service usage, and theservice processor 115 then periodically, or in response to a request,synchronizes the cost of service usage with, for example, the centralbilling 1619. In some embodiments, the service processor 115 utilizesthe service usage counter to determine whether the user is exceedingand/or is projected to exceed their current service plan for data usage,and then various actions can be performed as similarly described hereinto allow the user to modify their service plan and/or modify (e.g.,throttle) their network data usage. In some embodiments, the serviceusage counter can support providing to the user the following serviceusage related data/reports: service usage, known usage and estimatedusage, projected usage, present costs, projected costs, cost to roam,cost to roam options, and/or projected roaming costs. For example,including a local service data usage counter on the device 101 allowsthe service processor 115 to more accurately monitor service data usage,because, for example, network (and/or billing) service usage countersmay not accurately also include, for example, control plane data trafficsent to/from the device 101 in their monitored service data usage count.

In some embodiments, verifiable device based service billing solutionsare provided. For example, as described herein, various device basedservice billing solutions can include a wide range of verificationtechniques to ensure that the device is properly reporting servicebilling events (e.g., to verify/ensure that the service billing is notmalfunctioning and/or has not been tampered with/compromised such thatit is not accurately or timely providing service billing information).As described herein, service billing generally refers the billing forone or more services for a device, such as device 101 (e.g., emailservice billing for data usage associated with received/sent emailrelated data over the access network 1610, web browsing service billingfor data usage associated with received/sent web browsing related dataover the access network 1610 and/or any other network based service,and/or any transactional based services, such as for multimedia contentpurchases or other transactions).

In some embodiments, verifiable device based service billing is providedby sending dummy(/test) billing events, such as having an access controlintegrity server 1654 of the service controller 122 instruct the accesscontrol integrity agent 1694 to send a dummy(/test) billing event to thebilling agent 1695. If the billing agent does not then send the expectedreport, which should reflect the dummy(/test) (or fails to timely sendany report), then the system can verify whether the billing process isworking properly. In addition, a dummy(/test) transaction can be used toverify transaction based billing through a variety of approaches (e.g.,the access control integrity agent 1694 can similarly send adummy(/test) transactional billing event to the billing agent 1695 as atest to determine whether the billing agent 1695 then provides theexpected report reflecting that dummy(/test) transaction). For example,the test billing events can be trapped by a device assisted billingmediation server and removed from the user account billing.

In some embodiments, verifiable device based service billing is providedby sending one or more data bursts to the device to confirm that datawas received and to confirm that the service monitor agent 1696 properlylogged the data burst(s) in the local service usage or service activitycounter. In some embodiments, data bursts can be used to verify datathrottling (e.g., if the device has exceeded service data usage limitsand/or is approaching such limits such that service data usage should bethrottled, then sending data bursts can be used to verify whether theexpected throttling is properly being performed on the device). In someembodiments, verifiable device based service billing is provided bysubmitting requests to connect to an unauthorized service/website toverify if that unauthorized service usage is properly blocked. In someembodiments, verifiable device based service billing is provided bysubmitting requests to perform an unauthorized transaction to verify ifthat unauthorized transaction is properly blocked.

In some embodiments, verifiable device based service billing is providedby verifying device service activities relative to IPDRs for the device.In some embodiments, the IPDRs for the device (possibly in a modifiedformat) are periodically and/or upon request sent to the device, asdescribed herein. For example, IPDRs for the device can be compared tothe device's local service data usage counter and/or to the service planfor the device to determine if the overall service data usage limit hasbeen exceeded, whether out of plan/unauthorized/unrecordedwebsites/other services have been performed by the device, whetherservice plan/profile bandwidth limits have been exceeded, whether out ofplan/unauthorized/unrecorded transactions have been performed (e.g.,verifying IPDR transaction logs, assuming such are included in theIPDRs, with the local transaction logs of the device to determine, forexample, whether the local device records indicate that fewer than thenetwork recorded number of content downloads, such as downloaded songs,were purchased), and/or whether any other activities verifiable based ona comparison of IPDRs indicate that the device has been used in anymanner that is out of or exceeds the service plan/profile for thedevice.

In some embodiments, device based service billing includes recordingbilling option response history. For example, this approach can beparticularly important for service plan overage conditions (e.g., whenthe use of the device is exceeding the service plan associated with thedevice in some manner, such as service data usage, bandwidth, service ortransaction access and/or in some other manner). In some embodiments, ina service plan overage condition, the user is requested to confirm thatuser has acknowledged notification of service plan overage, such as viathe user interface 1697. In some embodiments, such service plan overageacknowledgements require that the user enter a unique identification tovalidate authorization by the user identity associated with the device(e.g., another type of verification mechanism, in the event a device isstolen or being used by someone other than the authorized user of thedevice, then that unauthorized user would not be able to confirm theservice plan overage acknowledgement, and appropriate actions can thenbe taken, such as throttling, quarantining or (temporarily) suspendingservice/network access). In some embodiments, if the device iscompromised/hacked (e.g., by the user of the device), and the device isused in a manner that results in a service usage overage (e.g.,determined based on device assisted service usage monitoring, and/ornetwork based service usage monitoring using IPDRs/CDRs), then thebilling system determines billing for such service usage overage costs.This overage billing can be initiated by the device 100 (e.g., serviceprocessor 115), the service controller 122, the billing system 123, theAAA 121, or some other network function. In some embodiments, if thedevice is compromised/hacked (e.g., by a user of the device), and thedevice is used in a manner that results in a service usage overage, oneor more of the following actions is taken: the user is notified, theuser is required to acknowledge the notification, the device traffic issent to SPAN (or similar traffic sampling and analysis function), and/orthe device is flagged for further analysis.

In some embodiments, device based service billing includes an option tobill by account, such as to bill different service activities and/ortransactions to a specified account (e.g., other than the user's accountassociated with the general service plan for the device). For example,bill by account can provide for billing according to application,content type, website, transaction, network chatter (e.g., heartbeatcommunications and/or other network traffic that is used by, forexample, the central/service provider to generally maintain networkaccess for the device), and/or transaction partner sponsored activitiesand then report such bill by account information for billingmediation/reconciliation. For example, a bill by account report can besent by billing agent 1695 from the device to central billing 1619(e.g., as a billing event); or alternatively, sent to an intermediateserver/aggregator, which can then reformat and send the reformattedreport to central billing 1619 (e.g., providing the billing report in aformat required by central billing 1619); or alternatively, sent to amediation server, which can re-compute the billing based on the bill byaccount report (e.g., offset the bill based on network chatter,transaction based billing, transaction partner sponsored activities,content providers, website providers and/or advertising providers) andthen send the recomputed (and potentially reformatted) report to centralbilling 1619.

In some embodiments, one or more of the mediation/reconciliationfunctions for device assisted billing, device generated billing events,device generated bill by account events and device generated opentransaction billing events can be implemented in the service controller122 (e.g., the billing event server 1662) or in another function locatedin the billing system 123 or elsewhere. This billing mediation serverfunction accepts the device based billing events discussed immediatelyabove, reformats the billing events into a format accepted andrecognized by the billing system, mediates the billing event informationto remove service usage billing from the user account and place it inother bill by account categories as appropriate according to the bill byaccount mediation rules, adds other billing events for service usage ortransactions to the user account as appropriate according to the devicebased billing rules, and then applies the information to the billinginformation the user account to correct or update the account.

For example, a bill by account can allow for a website provider, such asGoogle or Yahoo, to pay for or offset certain account usage for webbrowsing, web based searching, web based email, or any other web basedor other service usage activities, which may also be based (in whole orin part) on the activities performed by the user on such transactionalservices (e.g., based on advertisement viewing/accessing orclick-through activities by the user, by which an advertisement businessmodel used by such website providers directly or indirectly supportssuch service account subsidies). As another example, a bill by accountcan allow for an advertiser to pay for or offset certain account usagefor viewing and/or accessing (e.g., clicking through) a web placedadvertisement or other advertisement sent via the network to the device.As yet another example, various network chatter (e.g., heartbeat relatednetwork and other network chatter related service data usage) can beassigned to a dummy account and such can be used to offset the billand/or used for tracking the data usage for such activities for thedevice. In another example, service data usage for access to atransactional service, such as a multimedia content download service(e.g., music, eBook, music/video streaming, and/or movie or othermultimedia content download service), or an online shopping site (e.g.,Amazon, eBay or another online shopping site), can be billed to atransactional service account assigned to a transactional servicepartner that sponsors access to that sponsor's transactional service,thereby allowing that transactional service partner to pays for oroffset (e.g., subsidize) the account usage for such activities, whichmay also be based (in whole or in part) on the transactions actuallyperformed by the user on such transactional services (e.g., based on thevolume/cost of the multimedia service download purchases by the userand/or online activities).

In some embodiments, device based service billing includes recordingbilling events on the device and then reporting such billing to thenetwork (e.g., central billing 1619). In some embodiments, device basedservice billing includes reporting service usage events and/or applyingcost look-up and logging/reporting service billing updates. For example,this allows for reporting not only service usage but also cost of suchservice usage to the user via the user interface of device 101. Also,for example, the cost of such service usage can also be reported to thebilling server. In some embodiments, device based service billingincludes reporting service usage to the network, and the networkdetermines the cost for such service usage.

In some embodiments, billing information for roaming partners isprovided. For example, a roaming server can include a roaming servicecost data table for roaming service partners. In this example, when thedevice (e.g., device 101) connects to a roaming network provided by aroaming service partner, then the device can also receive the roamingservice data rate based on the roaming service cost data table providedby the roaming server. Alternatively, the roaming server can send theroaming service cost data table (or a modified format of the same) tothe device thereby allowing the device to determine the costs for suchroaming network service usage or service activity. As described herein,the device can also automatically use a roaming service profile whenconnecting to the roaming network service and/or the user can benotified of the roaming service profile options based on the roamingservice data costs and then select the desired roaming service profileaccordingly.

In some embodiments, the user is provided with a list of service costsbased on locally stored roaming table and a search of available roamingpartners that the device 100 detects and can connect to. In someembodiments, the user is provided with a projected cost per day for oneor more roaming service provider options based on typical service usagehistory and the cost for each service provider. In some embodiments, theuser is provided with a set of options for service usage notification,controlling or throttling service usage and/or cost while roaming (e.g.,using the service notification and cost control techniques as similarlydiscussed herein but applied to the roaming network). In someembodiments, these controls are set by a VSP (or, e.g., an IT managerusing VSP functions). In some embodiments, roaming tables are updatedperiodically in the background while on a home network (or other lowcost network) and cached. In some embodiments, cache updates occur basedon fixed time period (e.g., late at night when updates are lessexpensive due to network inactivity). In some embodiments, the roamingpartner cost table cache updates are done whenever connected to adesirable network that is not as expensive or bandwidth constrained(e.g., at home, work, or off the WWAN). In some embodiments, updatesoccur at time of day that network is not busy. In some embodiments,updates occur based on network push when roaming table is changed (e.g.,one or more of the roaming partners changes the rate). In someembodiments, the service cost to update the roaming service cost tableis charged to bill by account and possibly not charged to end user. Insome embodiments, the roaming service center is provided as a servicethat is paid for (e.g., potentially bill by account tracks all relatedcosts). For example, this type of roaming cost control can be providedas a service through central provider, MVNO, roaming partner provider,VSP or as a third party application not associated with any serviceprovider (e.g., IT manager). For example, the controls for how to updatecache, set service control policies, and other controls can be definedby any number of VSP entities including the user through a websiteservice.

In some embodiments, a roaming service center is provided as a servicein which, for example, the user is provided with a list of service costsbased on a locally stored (or remotely accessed) roaming table. In someembodiments, the roaming service center provides the user with aprojected cost per day for one or more roaming service provider optionsbased on typical service usage history and the cost for each serviceprovider. In some embodiments, the roaming service center provides theuser with a set of options for controlling/throttling usage and/or costwhile roaming. In some embodiments, these controls are set by a VSP(e.g., an IT manager using VSP functions). For example, roaming tablescan be updated periodically in the background while on a home networkand cached. In some embodiments, cache updates occur based on a fixedtime period. In some embodiments, the roaming partner cost table cacheupdates are done whenever the device is connected to a desirable networkthat is not as expensive or bandwidth constrained (e.g., at home, workand/or off the WWAN). In some embodiments, updates occur at time of daythat network is not busy. In some embodiments, updates occur based on anetwork push when a roaming table is changed (e.g., one or more of theroaming partners changes the rate). In some embodiments, the servicecost to update the roaming service cost table is charged to bill byaccount and possibly not charged to the user. In some embodiments, theroaming service center is provided as a service that is paid for by theuser and/or part of a service plan. In some embodiments, a bill byaccount function tracks all related costs. For example, the roamingservice center can be provided as a service through central provider,MVNO, roaming partner provider, VSP or as a third party application notassociated with any service provider (e.g., IT manager).

In some embodiments, a synchronized local service usage counter based ontime stamped central billing information is provided. For example, thelocal service usage counter, as similarly described above, can also besynchronized to past service usage records (e.g., time stamped centralbilling records of service usage for the device) and use local estimatesfor current/present service usage estimates for the device. In thisexample, the central billing system (e.g., central billing 1619) canpush the time stamped central billing information to the device (e.g.,device 101), the device can pull the time stamped central billinginformation, and/or an intermediate server can provide a mediated pushor pull process. In some embodiments, synchronization is performingperiodically based on service usage levels with free-running estimatesbetween synchronizations.

In some embodiments, service usage is projected based on calculatedestimates of service usage based on synchronized service usage and localservice usage count information. For example, projected service usagecan be calculated on the device or calculated on a server (e.g., abilling server or an intermediate billing server), which provides thecalculated projected service usage information to the device, such asusing various adaptive algorithms for service usage projections. Forexample, an adaptive algorithm can use historical/past synchronizednetwork service usage information (e.g., synchronized with local serviceusage data based on time stamps associated with IPDRs) to assist inservice usage projections, based on, for example, total service usagecount, service usage count by certain service related criteria (e.g.,application, content, service type, website and/or time of day). Inanother example, an adaptive algorithm synchronizes to past serviceusage data (e.g., the local estimate of past service usage data isupdated to be synchronized up through the point in time associated withthe latest IPDR time stamp that has been received) and current localestimates of service usage collected since the latest time stamp arethen added to the time stamped IPDR service usage counter to minimizethe service usage counter offset so that it is no greater than thedifference between the network service usage measure and the localservice usage measure since the latest IPDR time stamp. In someembodiments, these adaptive algorithm techniques are performed on thedevice and/or performed on the network (e.g., on a network server) forprocessing. In some embodiments, if there is an offset in the localdevice based service usage count between IPDR synchronization events andthe IPDR service usage count between IPDR synchronization events, thenan algorithm can be employed to estimate any systematic sources for theoffset and correct the local service usage count to minimize theoffsets. As an example, if the IPDR service usage count is typically offby a fixed percentage, either high or low, then an algorithm can beemployed to estimate a multiplier that is applied to the local serviceusage count to minimize the offset between IPDR service usagesynchronization events. In another example, there can be a consistentconstant offset and a multiplier offset, both of which can be estimatedand corrected for. Those of ordinary skill in the art will appreciatethat more sophisticated algorithms can be employed to estimate thenature of any systematic offsets, including, for example, offsets thatoccur due to specific service usage activities or network chatter tomanage the device, and such offsets can then be minimized between IPDRservice synchronization events. In some embodiments, synchronizedservice usage data is used to create an improved analysis of thestatistical patterns of service usage to provide more accurate serviceusage projections. Those of ordinary skill in the art will alsoappreciate that a variety of additional adaptive algorithm techniquescan be used including those that provide for various statisticalanalysis techniques and/or other techniques.

In some embodiments, service usage is projected for the end of abilling/service period for a service plan versus the service usageallowed under the service plan for that billing/service period. Adisplay of excess charges is also provided for the projected rate ofservice usage based on the monitored service usage behavior through theend of the billing/service period (e.g., this can be zero if the serviceusage is projected to be less than that allowed under the service planand a positive cost number if it is projected to be more than theservice plan). For example, this can be implemented in numerous ways,such as on a server in the network, on a gateway/router/switch in thenetwork, and/or on the device, as discussed below and generallydescribed herein with respect to other service/cost usage monitoring andnotification embodiments. If implemented in the network server orgateway/router/switch, then the service/cost usage projections andrelated information can be pushed to the device, or the device can benotified that such information is available to pull and/or periodicallypushed/pulled. The service usage information/estimates can be collectedfrom the device, the network or both (e.g., reconciled and/orsynchronized) as similarly described herein. The service usageinformation/estimates are then analyzed to determine service usage/costprojects as similarly described herein and compared to the service planfor the device to determine the projected service/cost usage overage (ifany). In some embodiments, one or more of the following are determinedby, reported to and/or displayed on the device: service usage value,projected service usage value, service usage plan limit, projectedservice usage overage, projected service cost overage, service planperiod time duration, service plan time remaining before end of periodand/or other pertinent information.

In some embodiments, the device also determines service costs based onthe synchronized service usage count thereby allowing the device to alsoreport the service cost information to the user. For example, the devicecan locally store a service cost look-up table(s), locally storedifferent service cost look-up tables for different networks and/or forroaming networks, and/or request such information from a billing orintermediate billing server (and/or a roaming server) on the network. Asanother example, the device can obtain the calculated service costsbased on the synchronized local service usage count and/or networkservice usage count from an intermediate server (e.g., a billing orintermediate billing server) thereby offloading the computational costsassociated with calculated these projections and the data storage forservice cost lookup tables onto the intermediate server on the networkusing the network service usage counter with or, alternatively, withoutthe synchronized local service usage counter.

In some embodiments, service usage count categorization by network(e.g., a home network (such as a Wi-Fi, WAN, femtocell or other homenetwork) versus a roaming network) is provided. Similarly, thesynchronized local service usage counter can be synchronized by network.Also, a synchronized local service usage count for networks controlledby a central provider, for networks controlled by other providers (e.g.,MVNO), and/or free networks can similarly be provided.

In some embodiments, a service notification and billing interface isprovided. For example, service usage and projected service usage, suchas described herein, can be displayed to the user of the device (e.g.,via user interface 1697). Similarly, expected/projected service or costoverrun/overage, such as described herein, can also be displayed to theuser. As another example, a most cost effective plan can bedetermined/projected based on historical and/or projected service usage,and this determined/projected most cost effective plan can be displayedto the user. In yet another example, a list of available networksaccessible by the device can be displayed to the user. In this example,one or more undesired available networks can also be blocked fromdisplay thereby only displaying to the user desired and/or preferredavailable networks. In this example, service usage plans and/or serviceusage plan option comparison for one or more alternative networks orroaming networks can also be displayed to the user. Similarly, servicecost plans and/or service/cost plan option comparison for one or morealternative networks or roaming networks can also be displayed to theuser. In addition, roaming service usage, projected roaming serviceusage, estimated roaming service cost, and/or projected estimatedroaming service cost can also be displayed to the user. These roamingservice usage/costs can also be displayed to the user so that the usercan utilize this information for selecting various roaming servicebilling options. In another example, alternative and/or least costnetworks are determined and displayed to the user. In another example,alternative warnings are displayed to the user for any or specifiedroaming networks.

In some embodiments, the service notification and billing interfacenotifies the user of expected network coverage (e.g., based on thedevice's current geography/location and the accessible networks for thedevice from that current geography/location) and displays options to theuser based on the expected network coverage information. In someembodiments, the service notification and billing interface notifies theuser of their current service usage at specified service usage pointsand displays various options to the user (e.g., service usage optionsand/or billing options). For example, the user's responses to thepresented options are recorded (e.g., stored locally on the device atleast temporarily for reporting purposes or permanently in a localconfiguration data store until such configuration settings are otherwisemodified or reset) and reported, such as to the billing server (e.g.,central billing 1619). For example, user input, such as selected optionsand/or corresponding policy settings, can be stored locally on thedevice via a cache system. As another example, the service notificationand billing interface displays options to the user for how the userwants to be notified and how the user wants to control service usagecosts, the user's input on such notification options is recorded, andthe cost control options (e.g., and the billing agent 1695 and policycontrol agent 1692) are configured accordingly. Similarly, the user'sinput on service plan options/changes can be recorded, and the serviceplan options/changes (e.g., and the billing agent 1695 and policycontrol agent 1692) are configured/updated accordingly. In anotherexample, the service notification and billing interface provides varioustraffic control profiles, such as for where the user requests assistancein controlling service usage costs (e.g., service data usage and/ortransactional usage related activities/costs). Similarly, the servicenotification and billing interface can provide various notificationoptions, such as for where the user wants advance warning on servicecoverage. In another example, the service notification and billinginterface provides options for automatic pre-buy at a set point inservice usage. In another example, the service notification and billinginterface provides the option to choose different notification and costcontrol options for alternative networks or roaming networks.

In some embodiments, an online portal or web server is provided forallowing the user to select and/or update policy settings. For example,user input provided via the online portal/web server can be recorded andreported to the billing server (e.g., central billing 1619). In anotherexample, the online portal/web server can display transaction billinginformation and/or accept input for a transaction billing request, whichcan then be reported to the billing server accordingly.

As shown in FIG. 16, the service processor 115 includes a serviceinterface or user interface 1697. In some embodiments, the userinterface 1697 provides the user with information and accepts userchoices or preferences on one or more of the following: user serviceinformation, user billing information, service activation, service planselection or change, service usage or service activity counters,remaining service status, service usage projections, service usageoverage possibility warnings, service cost status, service costprojections, service usage control policy options, privacy/CRM/GPSrelated options, and/or other service related information, settings,and/or options. For example, the user interface 1697 can collect serviceusage information from service monitor agent 1696 to update the localservice usage counter (and/or, alternatively, the service usageinformation is obtained from the service controller 122) to update userinterface service usage or service cost information for display to theuser. As another example, service billing records obtained from centralbilling system 1619 can be used to synchronize local service usagecounters and service monitor agent 1696 information to perform real-timeupdating of local service usage counters between billing system 1619synchronizations. As another example, the user interface 1697 candisplay options and accept user preference feedback, such as similarlydiscussed above with respect to user privacy/CRM/GPS filtering, trafficmonitoring and service controls. For example, the user interface 1697can allow the user of the device to modify their privacy settings,provide user feedback on service preferences and/or service experiences,modify their service profiles (e.g., preferences, settings,configurations, and/or network settings and options), to review serviceusage data (e.g., based on local service usage counters and/or otherdata monitored by the service processor 115), to receive various eventsor triggers (e.g., based on projected service usage/costs), and/or theuser interface 1697 can provide/support various other user input/outputfor service control and service usage.

In some embodiments, by providing the service policy implementation andthe control of service policy implementation to the preferences of theuser, and/or by providing the user with the option of specifying orinfluencing how the various service notification and control policies orcontrol algorithms are implemented, the user is provided with optionsfor how to control the service experience, the service cost, thecapabilities of the service, the manner in which the user is notifiedregarding service usage or service cost, the level of sensitive userinformation that is shared with the network or service provider entity,and the manner in which certain service usage activities may or may notbe throttled, accelerated, blocked, enabled and/or otherwise controlled.Accordingly, some embodiments provide the service control tobeneficially optimize user cost versus service capabilities orcapacities in a manner that facilitates an optimized user experience anddoes not violate network neutrality goals, regulations and/orrequirements. For example, by offering the user with a set of choices,ranging from simple choices between two or more pre-packaged servicecontrol settings options to advanced user screens where more detailedlevel of user specification and control is made available, someembodiments allow the service provider, device manufacturer, devicedistributor, MVNO, VSP, service provider partner, and/or other “entity”to implement valuable or necessary service controls while allowing theuser to decide or influence the decision on which service usageactivities are controlled, such as how they are controlled or throttledand which service usage activities may not be throttled or controlled insome manner. These various embodiments allow the service provider,device manufacturer, device distributor, MVNO, VSP, service providerpartner, or other “entity” to assist the user in managing services in amanner that is network neutral with respect to their implementation andservice control policies, because the user is making or influencing thedecisions, for example, on cost versus service capabilities or quality.By further providing user control or influence on the filtering settingsfor the service usage reporting or CRM reporting, various levels ofservice usage and other user information associated with device usagecan be transmitted to the network, service provider, devicemanufacturer, device distributor, MVNO, VSP, service provider partner,and/or other “entity” in a manner specified or influenced by the user tomaintain the user's desired level of information privacy.

As shown in FIG. 16, the service processor 115 includes the servicedownloader 1663. In some embodiments, the service downloader 1663provides a download function to install or update service softwareelements on the device. In some embodiments, the service downloader 1663requires a secure signed version of software before a download isaccepted. For example, the download can require a unique key for aparticular service downloader 1663. As another example, the servicedownloader 1663 can be stored or execute in secure memory or execute asecure memory partition in the CPU memory space. Those of ordinary skillin the art will appreciate that there are a variety of other securitytechniques that can be used to ensure the integrity of the servicedownloader 1663.

As shown in FIG. 16, the service processor 115 includes a modem driver1640. In some embodiments, the modem driver 1640 converts data trafficinto modem bus (not shown) traffic for one or more modems via the modemfirewall 1655. As shown in FIG. 18, in some embodiments, modem selectionand control 1811 selects the access network connection and is incommunication with the modem firewall 1655, and modem drivers 1831,1815, 1814, 1813, 1812 convert data traffic into modem bus traffic forone or more modems and are in communication with the modem selection andcontrol 1811. As shown in FIG. 21, in some embodiments, modems 2141,2125, 2124, 2123, 2122, which are in communication with the modem bus2120, connect the device to one or more networks. In some embodiments,different profiles are selected based on the selected network connection(e.g., different service profiles/policies for WWAN, WLAN, WPAN,Ethernet and/or DSL network connections), which is also referred toherein as multimode profile setting. For example, service profilesettings can be based on the actual access network (e.g., home DSL/cableor work network) behind the Wi-Fi not the fact that it is Wi-Fi (or anyother network, such as DSL/cable, satellite, or T-1), which is viewed asdifferent than accessing a Wi-Fi network at the coffee shop. Forexample, in a Wi-Fi hotspot situation in which there are a significantnumber of users on a DSL or T-1 backhaul, the service controller can sitin a service provider cloud or an MVNO cloud, the service controls canbe provided by a VSP capability offered by the service provider (e.g.,as described herein with respect to FIG. 49) or the service controllercan be owned by the hotspot service provider that uses the servicecontroller on their own without any association with an access networkservice provider. For example, the service processors can be controlledby the service controller to divide up the available bandwidth at thehotspot according to QoS or user sharing rules (e.g., with some usershaving higher differentiated priority (potentially for higher servicepayments) than other users). As another example, ambient services (assimilarly described herein) can be provided for the hotspot for verifiedservice processors.

In some embodiments, the service processor 115 and service controller122 are capable of assigning multiple service profiles associated withmultiple service plans that the user chooses individually or incombination as a package. For example, a device 100 starts with ambientservices that include free transaction services wherein the user paysfor transactions or events rather than the basic service (e.g., a newsservice, eReader, PND service, pay as you go session Internet) in whicheach service is supported with a bill by account capability to correctlyaccount for any subsidized partner billing to provide the transactionservices (e.g., Barnes and Noble may pay for the eReader service andoffer a revenue share to the service provider for any book or magazinetransactions purchased form the device 100). In some embodiments, thebill by account service can also track the transactions and, in someembodiments, advertisements for the purpose of revenue sharing, allusing the service monitoring capabilities disclosed herein. Afterinitiating services with the free ambient service discussed above, theuser may later choose a post-pay monthly Internet, email and SMSservice. In this case, the service controller 122 would obtain from thebilling system 123 in the case of network based billing (or in someembodiments the service controller 122 billing event server 1622 in thecase of device based billing) the billing plan code for the newInternet, email and SMS service. In some embodiments, this code is crossreferenced in a database (e.g., the policy management server 1652) tofind the appropriate service profile for the new service in combinationwith the initial ambient service. The new superset service profile isthen applied so that the user maintains free access to the ambientservices, and the billing partners continue to subsidize those services,the user also gets access to Internet services and may choose theservice control profile (e.g., from one of the embodiments disclosedherein). The superset profile is the profile that provides the combinedcapabilities of two or more service profiles when the profiles areapplied to the same device 100 service processor. In some embodiments,the device 100 (service processor 115) can determine the supersetprofile rather than the service controller 122 when more than one“stackable” service is selected by the user or otherwise applied to thedevice. The flexibility of the service processor 115 and servicecontroller 122 embodiments described herein allow for a large variety ofservice profiles to be defined and applied individually or as a supersetto achieve the desired device 100 service features.

As shown in FIG. 16, the service controller 122 includes a servicecontrol server link 1638. In some embodiments, device based servicecontrol techniques involving supervision across a network (e.g., on thecontrol plane) are more sophisticated, and for such it is increasinglyimportant to have an efficient and flexible control plane communicationlink between the device agents (e.g., of the service processor 115) andthe network elements (e.g., of the service controller 122) communicatingwith, controlling, monitoring, or verifying service policy. For example,the communication link between the service control server link 1638 ofservice controller 122 and the service control device link 1691 of theservice processor 115 can provide an efficient and flexible controlplane communication link, a service control link 1653 as shown in FIG.16, and, in some embodiments, this control plane communication linkprovides for a secure (e.g., encrypted) communications link forproviding secure, bidirectional communications between the serviceprocessor 115 and the service controller 122. In some embodiments, theservice control server link 1638 provides the network side of a systemfor transmission and reception of service agent to/from network elementfunctions. In some embodiments, the traffic efficiency of this link isenhanced by buffering and framing multiple agent messages in thetransmissions (e.g., thereby reducing network chatter). In someembodiments, the traffic efficiency is further improved by controllingthe transmission frequency and/or linking the transmission frequency tothe rate of service usage or traffic usage. In some embodiments, one ormore levels of security and/or encryption are used to secure the linkagainst potential discovery, eavesdropping or compromise ofcommunications on the link. In some embodiments, the service controlserver link 1638 also provides the communications link and heartbeattiming for the agent heartbeat function. As discussed below, variousembodiments described herein for the service control server link 1638provide an efficient and secure mechanism for transmitting and receivingservice policy implementation, control, monitoring and verificationinformation between the device agents (e.g., service processoragents/components) and other network elements (e.g., service controlleragents/components).

In some embodiments, the service control server link 1638 can employ thecounterpart service control plane secure transmission methods discussedabove with respect to the service control device link 1691. For example,one or more layers of security can be used to secure the communicationslink, including, for example, basic IP layer security, TCP layersecurity, service control link layer security, and/or security specificfrom service controller servers to service processor agents.

In some embodiments, the service control server link 1638 reducesnetwork chatter by efficiently transmitting service control relatedcommunications over the link. For example, the service control serverlink 1638 can transmit server messages asynchronously as they arrive. Asanother example, the service control server link 1638 can performcollection or buffering of server messages between transmissions. Asanother example, the service control server link 1638 can determine whento transmit based potentially on several parameters, such as one or moreof: periodic timer trigger, waiting until a certain amount of serviceusage or traffic usage has occurred, responding to a service agentmessage, responding to a service agent request, initiated by one or moreservers, initiated by a verification error condition, and/or initiatedby some other error condition. For example, once a transmission triggerhas occurred, the service control server link 1638 can take all bufferedagent communications and frame the communications. In addition, theservice control server link 1638 can provide for an efficientcommunication link based on various embodiments related to the timing oftransmissions over the service control link, as similarly discussedabove with respect to the service control device link 1691 description.For example, the timing functions, such as asynchronous messages orpolling for messages, constant frequency transmission, transmissionbased on how much service usage or data traffic usage has taken place,transmission in response to device side control link message, serviceverification error events, other error events, and/or other messagetransmission trigger criteria can be determined, controlled and/orinitiated by either the device side or the network side depending on theembodiment.

In some embodiments, the service control server link 1638 provides forsecuring, signing, encrypting and/or otherwise protecting thecommunications before sending such communications over the servicecontrol link 1653. For example, the service control server link 1638 cansend to the transport layer or directly to the link layer fortransmission. In another example, the service control server link 1638further secures the communications with transport layer encryption, suchas TCP TLS or another secure transport layer protocol. As anotherexample, the service control server link 1638 can encrypt at the linklayer, such as using IPSEC, various possible VPN services, other formsof IP layer encryption and/or another link layer encryption technique.

In some embodiments, the service control server link 1638 includes theagent heartbeat function in which the agents provide certain requiredreports to the service processor for the purpose of service policyimplementation verification or for other purposes. For example, theheartbeat function can also be used to issue queries or challenges,messages, service settings, service control objectives, informationrequests or polling, error checks and/or other communications to theagents. As another example, agent heartbeat messages can be in the openor encrypted, signed and/or otherwise secured. Additional heartbeatfunction and the content of heartbeat messages can be provided assimilarly described herein, such as described above with respect to theservice control device link 1691 and the access control integrity agent1694 and other sections. In some embodiments, the service controller 122and/or agents of the service controller 122 are programmed toperiodically provide reports, such as upon a heartbeat response (e.g.,an agent can repeatedly send necessary reports each heartbeat), andappropriate actions can then be taken based upon such received reports.Accordingly, the heartbeat function provides an important and efficientsystem in various embodiments described herein for verifying the servicepolicy implementation and/or protecting against compromise events. Thereare many other functions the agent heartbeat service can perform many ofwhich are discussed herein, while many others will be apparent to one ofordinary skill in the art given the principles, design background andvarious embodiments provided herein.

In some embodiments, the service control server link 1638 also providesa service control software download function for various embodiments,which, for example, can include a download of new service softwareelements, revisions of service software elements, and/or dynamicrefreshes of service software elements of the service processor 115 onthe device. In some embodiments, this function is performed by theservice control server link 1638 transmitting the service controlsoftware as a single file over the service control link. For example,the file can have encryption or signed encryption beyond any provided bythe communication link protocol itself for service control link 1653. Inanother example, the service control software files can besegmented/divided into smaller packets that are transmitted in multiplemessages sent over the service control link 1653. In yet anotherexample, the service control software files can be transmitted usingother delivery mechanism, such as a direct TCP socket connection from aservice download control server 1660, which can also involve securetransport and additional levels of encryption. In some embodiments, theservice control server link 1638 and/or service download control server1660 use(s) an agent serial number and/or a security key look up whenagents are updated and/or when a dynamic agent download occurs.

As shown in FIG. 16, the service controller 122 includes an accesscontrol integrity server 1654. In some embodiments, the access controlintegrity server 1654 collects device information on service policy,service usage, agent configuration and/or agent behavior. For example,the access control integrity server 1654 can cross check thisinformation to identify integrity breaches in the service policyimplementation and control system. In another example, the accesscontrol integrity server 1654 can initiate action when a service policyviolation or a system integrity breach is suspected.

In some embodiments, the access control integrity server 1654 (and/orsome other agent of service controller 122) acts on access controlintegrity agent reports and error conditions. Many of the access controlintegrity agent 1654 checks can be accomplished by the server. Forexample, the access control integrity agent 1654 checks include one ormore of the following: service usage measure against usage rangeconsistent with policies (e.g., usage measure from the network and/orfrom the device); configuration of agents; operation of the agents;and/or dynamic agent download.

In some embodiments, the access control integrity-server 1654 (and/orsome other agent of service controller 122) verifies device servicepolicy implementations by comparing various service usage measures(e.g., based on network monitored information, such as by using IPDRs,and/or local service usage monitoring information) against expectedservice usage behavior given the policies that are intended to be inplace. For example, device service policy implementations can includemeasuring total data passed, data passed in a period of time, IPaddresses, data per IP address, and/or other measures such as location,downloads, email accessed, URLs, and comparing such measures expectedservice usage behavior given the policies that are intended to be inplace.

In some embodiments, the access control integrity server 1654 (and/orsome other agent of service controller 122) verifies device servicepolicy, and the verification error conditions that can indicate amismatch in service measure and service policy include one or more ofthe following: unauthorized network access (e.g., access beyond ambientservice policy limits); unauthorized network speed (e.g., average speedbeyond service policy limit); network data amount does not match policylimit (e.g., device not stop at limit without re-up/revising servicepolicy); unauthorized network address; unauthorized service usage (e.g.,VOIP, email, and/or web browsing); unauthorized application usage (e.g.,email, VOIP, email, and/or web); service usage rate too high for plan,and policy controller not controlling/throttling it down; and/or anyother mismatch in service measure and service policy.

In some embodiments, the access control integrity server 1654 (and/orsome other agent of service controller 122) verifies device servicepolicy based at least in part on, for example, various error conditionsthat indicate a mismatch in service measure and service policy. Forexample, various verification error conditions that can indicate amismatch in service measure and service policy include one or more ofthe following: mismatch in one service measure and another servicemeasure; agent failure to report in; agent failure to respond to queries(e.g., challenge-response sequence and/or expected periodic agentreporting); agent failure to respond correctly to challenge/responsesequence; agent improperly configured; agent failure in self checks;agent failure in cross-checks; unauthorized agent communication orattempted unauthorized communication; failure in service policyimplementation test; failure in service usage reporting test; failure inservice usage billing test; failure in transaction billing test; failurein download sequence; environment compromise event, such as unauthorizedsoftware load or execution (or attempt), unauthorized memory access (orattempt), unauthorized agent access (or attempt), known harmfulsoftware, and/or known harmful communications signature; and/or failureto respond to various messages, such as send message and suspend and/orsend message and quarantine. In some embodiments, the access controlintegrity server 1654 (and/or some other agent of service controller122) verifies device service policy by performing automated queries andanalysis, which are then reported (e.g., anomalous/suspicious reportresults can be reported for further analysis by a person responsible fordetermining whether such activities indicate out of policy activities orto provide information to the user to inform the user of suchanomalous/suspicious report results that may indicate out of policyactivities). For example, the user can review the report to authorizewhether such activities were performed by the user (e.g., website accessrequests, specific transactions, and/or phone calls) and/or indicatethat such activities were not authorized by the user (e.g., indicate apotential compromise of the device, such as by malware or otherunauthorized software/user use of the device). In another example, theuser can also be connected to communicate with service support of theservice provider regarding such reported activities (e.g., by text/chat,voice/phone, and/or video conference to a service support). Accordingly,in some embodiments, the access control integrity server 1654 (and/orsome other agent of service controller 122) provides a policy/servicecontrol integrity service to continually (e.g., periodically and/orbased on trigger events) verify that the service control of the devicehas not been compromised and/or is not behaving out of policy.

In some embodiments, upon detection of one or more service verificationerrors, such as the various service verification errors discussed above,the device is directed to a quarantine network status in which thedevice can, for example, only access network control plane functions,billing functions, and other functions generally controlled by theaccess network service provider or the central service provider. Forexample, quarantine network access restrictions and routing can beaccomplished with the access network AAA and routing system (e.g.,access network AAA server 1621 and one or more of the gateways 410, 420,508, 512, 520, 608, 612, 620, 708, 712, 720) or can be accomplished withdevice based access control or traffic control policy implementation.Quarantine network equipment or servers can, for example, be locatedwithin the access network or within another network with access to theaccess network. Communication with the quarantine network infrastructurecan be accomplished, for example, with a secure link with one or moreencryption levels or a dedicated private link. In some embodiments,quarantining a device includes, for example, a two step process forrouting quarantine network device traffic, first, to a quarantinetraffic handling router or server and, second, from there to the actualquarantine network infrastructure, with the route being determined bydevice parameters, user parameters, access service provider parametersor other parameters associated with the quarantine network routing. Insome embodiments, the device is completely suspended from the network inwhich, for example, the device can first issue a user interface messageto the user or issuing another form of a message to the user or servicesubscriber, such as via email, hard copy message and/or voice message.In some embodiments, the device network access, service capabilitiesand/or traffic shaping are limited, partially restricted or completelyrestricted, service capabilities. For example, these limitations and/orrestrictions can be implemented in the device and/or in the network. Forexample, implementing a device quarantine (e.g., using a RADIUS serverto quarantine the device) can involve assigning the device to adifferent billing profile.

In some embodiments, upon detection of one or more service verificationerrors, such as the various service verification errors discussed above,switch based port analysis is performed to further monitor the device(e.g., referred to as Switched Port Analyzer (SPAN) on Cisco switches,and various other vendors have different names for it, such as RovingAnalysis Port (RAP) on 3Com switches). In some embodiments, the deviceservice policy implementation behavior is monitored at a deeper level inthe network by copying device traffic in the switch so that it goes toboth an intended data path destination and to a specified port forswitch based port analysis (e.g., the traffic content can be analyzedand recorded using deep packet inspection (DPI) techniques, which canprovide a finer level of detail than the typical IPDR). For example, anadvantage of performing a switch based port analysis function is thatthe traffic need not be analyzed in real time, and a sample subset ofthe devices on the network can be selected for such analysis based on,for example, either identifying devices that have suspect service policyimplementation behavior and/or a regular sampling algorithm thateventually samples all devices, or some other selection approaches. Asanother example, a scheduled switch based port analysis sampling can beapplied that eventually rotates through all devices and designates ahigher priority in the sampling queue for devices that are suspect.

In some embodiments, switch based port analysis allows for off-linesampled or non-real-time DPI, as described above, as a verificationmeasure for the device based service control measures that areimplemented. In some embodiments, sophisticated DPI techniques are usedto enhance the content of the IPDRs so that they provide detailedinformation that can be made available in the network. For example, someof the DPI packet analysis may be redundant between the device and thenetwork, but this approach provides for a much finer grain validationfor the device based service and less reliance on the device for some ofthe service traffic analysis that service providers need. In someembodiments, the device control server functions and the service controlpolicy verification functions are implemented in an integratedhardware/software system (e.g., a gateway, server, router, switch, basestation, base station aggregator, AAA server cluster or any otherhardware or hardware/software system) located in the network that thenetwork level traffic inspection is accomplished in, or in one or moreservers integrated to operate in a coordinated manner with the DPIboxes. In some embodiments, the device control server functions and theservice control policy verification functions are implemented in anintegrated hardware/software system (e.g., a gateway, server, router,switch, base station, base station aggregator, AAA server cluster or anyother hardware or hardware/software system) located in the network thatprovides deep service control capability (e.g., using DPI techniques)for devices that have some or all of the service processor functionsinstalled and, in some embodiments, also providing coarser networkcontrol of the basics for devices that do not have a service processorinstalled in the device (e.g., such coarser network control functionsinclude max data rate and/or max total data).

In some embodiments, the SPAN function is used in a revolving periodicmanner as well to augment CDR data with deeper packet information forthe purpose of spot-checking device based service usage measures.Examples of where this can be beneficial include spot checking networkaddress access policies, spot checking ambient access policies, spotchecking billing event reports, spot checking intermediate networkingdevice/end point device count (via checking network source ordestination addresses, token, cookies or other credentials, etc). Forexample, the periodic SPAN can be scheduled for all devices equally, forcertain devices or users with higher priority, frequency or depth ofSPAN than others, higher priority, higher frequency or immediatepriority for devices with higher usage patterns or unusual usagepatterns, immediate or very high priority for devices with a policyviolation status.

In some embodiments, a combination traffic inspection and servicecontrol approach implements traffic and service control functions in thenetwork that are conducive for a network based implementation andimplements traffic and service control functions in the device that areeither more conducive for performing in the device or can only beperformed in the device (e.g., activities involving inspection oftraffic that is encrypted once it is transmitted to the network). Forexample, using this approach, activities that can be done in the networkare generally performed in the network and/or are more efficientlyperformed in the network than the device, and activities that are moreefficiently performed in the device or can only be performed in thedevice are performed in the device (e.g., depending on deviceprocessing/storage capabilities and/or other design/securityconsiderations). For example, the following are various traffic andservice control functions that, in some embodiments, are preferably orcan only be performed in the device: network based packet processingcapability limitations (e.g., encrypted traffic, application layerinformation unavailable once the traffic goes into the networking stack,other application/usage context information available on the device butnot in the network); information that is generally/preferably maintainedand processed locally in the device for network neutrality reasons(e.g., network neutrality issues can generally be efficientlyimplemented by keeping all, substantially all or at least some aspect ofdecisions on how to implement algorithms to control traffic local to thedevice and under user decision control, and/or by providing the userwith a set of pre-packaged choices on how to manage service usage orservice activity usage or manage service usage versus service cost orprice); information that is generally/preferably maintained andprocessed locally in the device for user privacy reasons (e.g., deeperlevels of traffic monitoring and service usage monitoring data where itis available for assisting the user in achieving the best, lowest costexperience and implementing a CRM filter function to the user so thatthe user can control the level of CRM the network is allowed to receive,such as with the higher levels of information being exchanged forsomething of value to the user, and/or user location information);information that is generally/preferably maintained and processedlocally in the device for the purpose of informing the user of servicecontrol settings or service activity usage or to adjust service activitycontrol settings or receive user feedback to choices regarding serviceusage policies or billing options (e.g., providing the user with a UIfor the purpose of monitoring an estimate of service usage and/ornotifying the user of at least some aspect of estimated service usage orprojected service usage, providing the user with a UI for the purpose ofmonitoring an estimate of service cost and/or notifying the user of atleast some aspect of estimated service cost or projected service cost,providing the user with a UI for the purpose of providing the user withone or more service usage and/or service cost notification messages thatrequire user acknowledgement and/or a user decision and obtaining orreporting the user acknowledgements and/or decisions, providing the userwith a UI for the purpose of providing the user with service optionsand/or service payment options, providing the user with a UI for thepurpose of obtaining user choice for such options when service usage orcost estimates are about to run over limits or have run over limits orare projected to run over limits, providing the user with a UI for thepurpose of monitoring or conducting open central billing transactions orother transactions, providing the user with a UI for the purpose ofselecting the service control techniques and/or policies and/oralgorithms and/or pre-packaged configurations that can be used to defineor partially define the service activity usage control policiesimplemented in the device service processor or the network servicecontrol equipment/billing system or a combination of both); servicecontrol for roaming on different networks that typically do not havecompatible DPI-type techniques with the home network; certain servicenotification and traffic control algorithms (e.g., stack-ranked activitystatistical analysis and control of only the high usage activities);and/or a function for assigning a device to a service experience orambient activation experience or virtual service provider (VSP) atvarious times from manufacturing to device distribution to a user of thedevice. In some embodiments, certain activities are implemented in thedevice as a solution for networks in which a new centralized DPIapproach is not possible, not economically feasible, or for any numberof reasons not an option or not a preferred option.

In some embodiments, a network based solution is provided for a morebasic set of services for all devices that do not have service controlcapabilities, and a super-set of services and/or additional services areprovided for devices that include a service processor. As describedherein, a service controller function can be located in various placesin the network in accordance with various embodiments. It should also benoted that various other embodiments described herein also employ ahybrid service control function performing certain service controlfunctions in the network (e.g., collecting network service usageinformation, such as IPDRs, and/or performing DPI related functions inthe network for collecting network service usage information and/orthrottling/shaping traffic) and service control functions in the device(e.g., service processor 115, which, for example, monitors service usagein the device and/or performs throttling or traffic shaping in thedevice and/or performs certain billing event recording and reportingfunctions that are aptly performed on the device).

In some embodiments, lower level service policy implementationembodiments are combined with a higher level set of service policysupervision functions to provide device assisted verifiable networkaccess control, authentication and authorization services.

In some embodiments, device based access control services are extendedand combined with other policy design techniques to create a simplifieddevice activation process and connected user experience referred toherein as ambient activation. As similarly discussed above, ambientactivation can be provided by setting access control to a fixeddestination, verifying access with IPDRs, verifying access by setting amax data rate and triggering off in the network if it exceeds the maxdata rate, and/or by various other techniques.

As shown in FIG. 16, service controller 122 includes a service historyserver 1650. In some embodiments, the service history server 1650collects and records service usage or service activity reports from theAccess Network AAA Server 1621 and the Service Monitor Agent 1696. Forexample, although service usage history from the network elements can incertain embodiments be less detailed than service history from thedevice, the service history from the network can provide a valuablesource for verification of device service policy implementation,because, for example, it is extremely difficult for a device error orcompromise event on the device to compromise the network based equipmentand software. For example, service history reports from the device caninclude various service tracking information, as similarly describedabove. In some embodiments, the service history server 1650 provides theservice history on request to other servers and/or one or more agents.In some embodiments, the service history server 1650 provides theservice usage history to the device service history 1618. In someembodiments, for purposes of facilitating the activation trackingservice functions (described below), the service history server 1650maintains a history of which networks the device has connected to. Forexample, this network activity summary can include a summary of thenetworks accessed, activity versus time per connection, and/or trafficversus time per connection. As another example, this activity summarycan further be analyzed or reported to estimate the type of service planassociated with the traffic activity for the purpose of bill sharingreconciliation.

As shown in FIG. 16, service controller 122 includes a policy managementserver 1652. In some embodiments, the policy management server 1652transmits policies to the service processor 115 via the service controllink 1653. In some embodiments, the policy management server 1652manages policy settings on the device (e.g., various policy settings asdescribed herein with respect to various embodiments) in accordance witha device service profile. In some embodiments, the policy managementserver 1652 sets instantaneous policies on policy implementation agents(e.g., policy implementation agent 1690). For example, the policymanagement server 1652 can issue policy settings, monitor service usageand, if necessary, modify policy settings. For example, in the case of auser who prefers for the network to manage their service usage costs, orin the case of any adaptive policy management needs, the policymanagement server 1652 can maintain a relatively high frequency ofcommunication with the device to collect traffic and/or service measuresand issue new policy settings. In this example, device monitored servicemeasures and any user service policy preference changes are reported,periodically and/or based on various triggers/events/requests, to thepolicy management server 1652. In this example, user privacy settingsgenerally require secure communication with the network (e.g., a secureservice control link 1653), such as with the policy management server1652, to ensure that various aspects of user privacy are properlymaintained during such configuration requests/policy settingstransmitted over the network. For example, information can becompartmentalized to service policy management and not communicated toother databases used for CRM for maintaining user privacy.

In some embodiments, the policy management server 1652 provides adaptivepolicy management on the device. For example, the policy managementserver 1652 can issue policy settings and objectives and rely on thedevice based policy management (e.g., service processor 115) for some orall of the policy adaptation. This approach can require less interactionwith the device thereby reducing network chatter on service control link1653 for purposes of device policy management (e.g., network chatter isreduced relative to various server/network based policy managementapproaches described above). This approach can also provide robust userprivacy embodiments by allowing the user to configure the device policyfor user privacy preferences/settings so that, for example, sensitiveinformation (e.g., geo-location data, website history) is notcommunicated to the network without the user's approval. In someembodiments, the policy management server 1652 adjusts service policybased on time of day. In some embodiments, the policy management server1652 receives, requests or otherwise obtains a measure of networkavailability and adjusts traffic shaping policy and/or other policysettings based on available network capacity.

In some embodiments, the policy management server 1652 performs aservice control algorithm to assist in managing overall network capacityor application QoS. In some embodiments, the policy management server1652 performs an algorithm to determine which access network is best toconnect to, such as based on network capacity or application QoS,service usage costs, and/or any other criteria. In some embodiments, thedevice is capable of connecting to more than one network, andaccordingly, device service policies can be selected/modified based onwhich network the device is connected to. In some embodiments, thenetwork control plane servers detect a network connection change from afirst network to a second network and initiate the service policyimplementation established for the second network. In other embodiments,the device based adaptive policy control agent (e.g., policy controlagent 1692 described herein) detects network connection changes from thefirst network to the second network and implements the service policiesestablished for the second network.

In some embodiments, when more than one access network is available, thenetwork is chosen based on which network is most preferred according toa network preference list or according to the network that optimizes anetwork cost function. For example, the preference list can bepre-established by the service provide and/or the user. For example, thenetwork cost function can be based on a minimum service cost, maximumnetwork performance, determining whether or not the user or device hasaccess to the network, maximizing service provider connection benefit,reducing connections to alternative paid service providers, and/or avariety of other network preference criteria. In other embodiments, thedevice detects when one or more preferred networks are not available,implements a network selection function or intercepts other networkselection functions, and offers a connection to the available servicenetwork that is highest on a preference list. For example, thepreference list can be set by the service provider, the user and/or theservice subscriber.

As shown in FIG. 16, service controller 122 includes a network trafficanalysis server 1656. In some embodiments, the network traffic analysisserver 1656 collects/receives service usage history for devices and/orgroups of devices and analyzes the service usage. In some embodiments,the network traffic analysis server 1656 presents service usagestatistics in various formats to identify improvements in networkservice quality and/or service profitability. In other embodiments, thenetwork traffic analysis server 1656 estimates the service qualityand/or service usage for the network under variable settings onpotential service policy. In other embodiments, the network trafficanalysis server 1656 identifies actual or potential service behaviors byone or more devices that are causing problems for overall networkservice quality or service cost.

As shown in FIG. 16, service controller 122 includes a beta test server1658. In some embodiments, the beta test server 1658 publishes candidateservice plan policy settings to one or more devices. In someembodiments, the beta test server 1658 provides summary reports ofnetwork service usage or user feedback information for one or morecandidate service plan policy settings. In some embodiments, the betatest server 1658 provides a mechanism to compare the beta test resultsfor different candidate service plan policy settings or select theoptimum candidates for further policy settings optimization.

As shown in FIG. 16, service controller 122 includes a service downloadcontrol server 1660. In some embodiments, the service download controlserver 1660 provides a download function to install and/or updateservice software elements (e.g., the service processor 115 and/oragents/components of the service processor 115) on the device, asdescribed herein.

As shown in FIG. 16, service controller 122 includes a billing eventserver 1662. In some embodiments, the billing event server 1662 collectsbilling events, provides service plan information to the serviceprocessor 115, provides service usage updates to the service processor115, serves as interface between device and central billing server 1619,and/or provides trusted third party function for certain ecommercebilling transactions.

As shown in FIG. 16, the Access Network AAA server 1621 is in networkcommunication with the access network 1610. In some embodiments, theAccess Network AAA server 1621 provides the necessary access network AAAservices (e.g., access control and authorization functions for thedevice access layer) to allow the devices onto the central provideraccess network and the service provider network. In some embodiments,another layer of access control is required for the device to gainaccess to other networks, such as the Internet, a corporate networkand/or a machine to machine network. This additional layer of accesscontrol can be implemented, for example, by the service processor 115 onthe device. In some embodiments, the Access Network AAA server 1621 alsoprovides the ability to suspend service for a device and resume servicefor a device based on communications received from the servicecontroller 122. In some embodiments, the Access Network AAA server 1621also provides the ability to direct routing for device traffic to aquarantine network or to restrict or limit network access when a devicequarantine condition is invoked. In some embodiments, the Access NetworkAAA server 1621 also records and reports device network service usage(e.g., device network service usage can be reported to device servicehistory 1618).

As shown in FIG. 16, the device service history 1618 is in networkcommunication with the access network 1610. In some embodiments, thedevice service history 1618 provides service usage data records used forvarious purposes in various embodiments. In some embodiments, the deviceservice history 1618 is used to assist in verifying service policyimplementation. In some embodiments, the device service history 1618 isused to verify service monitoring. In some embodiments, the deviceservice history 1618 is used to verify billing records and/or billingpolicy implementation. In some embodiments, the device service history1618 is used to synchronize and/or verify the local service usagecounter.

As shown in FIG. 16, the central provider billing server 1619 is innetwork communication with the access network 1610. In some embodiments,the central provider billing server 1619 provides a mediation functionfor central provider billing events. For example, the central providerbilling server 1619 can accept service plan changes. In someembodiments, the central provider billing server 1619 provides updateson device service usage, service plan limits and/or service policies. Insome embodiments, the central provider billing server 1619 collectsbilling events, formulates bills, bills service users, provides certainbilling event data and service plan information to the servicecontroller 122 and/or device 100.

Establishing Coordinated Service and Verification Policies for ServiceProcessor, Service Controller and Network Functions

In some embodiments, device and network apparatus coordinate one or moreof the following: network service policy implementation settings, deviceservice policy implementation settings, network service profileimplementation settings, device service profile implementation settings,network service usage measures used for the purpose of verifying servicepolicy implementation, device service usage measures used for thepurpose of verifying service policy implementation, network actionstaken upon detection of service usage policy violation and deviceactions taken upon detection of service usage policy violation. In someembodiments, local device settings for the service monitoring, usageand/or billing profile or policy settings used, for example, by a deviceservice processor 115, are associated with corresponding records for thevarious network apparatus that also rely upon the service policy andprofile settings to monitor, control and/or bill for services or torespond to out of policy service usage conditions. For example, suchnetwork apparatus include the service controller 122 or similarfunctions, the billing system 123 or similar functions, the network AAA121, gateways 410, 420, 508, 512, 520, 608, 612, 620, 708, 712, 720, orother networking equipment. In some embodiments, the service profile orpolicy settings are associated between the device and network in amanner that allows for effective and coordinated operation between thedevice service processor 115 and the network apparatus, but does notrequire an explicit function that simultaneously controls/coordinatesthe service policy or profile implementation and/or verification actionstaken by the device 100 (e.g., the service processor 115) and thenetwork apparatus. As an example, such embodiments can be applied inoverlay applications as discussed below.

In some embodiments, a network function (e.g., the service controller122, and/or more specifically the policy management server 1652function, or other similar function) obtain, derive or otherwisedetermine the association of the service profile or policy settings toprogram a device service processor 115 and the various network apparatusfunctions (e.g., possibly including but not limited to the servicecontroller 122 or similar functions, the billing system 123 or similarfunctions, the network AAA 121, gateways 410, 420, 508, 512, 520, 608,612, 620, 708, 712, 720, or other networking equipment) by reading,receiving, querying, pulling or otherwise obtaining the settings fromone or more of the network apparatus functions or from a data base thatstores the service policy or profile settings for one or more of thenetwork apparatus functions. After obtaining one or more of the networkapparatus settings, a mapping (e.g., an association) of the networkapparatus settings to the appropriate device 100 (service processor 115)settings can be determined to advantageously support the service usagemonitoring, service usage control, service usage billing or serviceusage verification objectives being addressed. The policy or profilesettings for the device can be a direct translation of the policy orprofile settings used for the network apparatus, or the device policy orprofile settings can be less directly derived from the network apparatuspolicy or profile settings. For example, service usage limits containedin the billing system 123 service plan can be either directly mapped tousage limit settings on the device service processor 115 (e.g., serviceusage stops when the limit is hit or the user is notified or the user isbilled), or the usage limits can be mapped to a number of serviceprofiles the user may select from (e.g., as discussed herein, the usercan select from options involving various actual usage versus usagelimit notification policies and/or service usage control, limitations orthrottling policies).

For example, the service usage policy or profile limits or allowancesmaintained for the network apparatus functions (e.g., the serviceprofile or service plan usage limits stored in the billing system 123 orAAA 121) can be read or queried by a network function (e.g., the servicecontroller 122 or the service controller 122 through a secondintermediary server connected to the billing system 123 and/or the AAAsystem 121), and the service usage limits stored in these networkingapparatus can be either directly translated to the settings for theservice processor 115 or may need to be interpreted, expanded orotherwise modified to obtain the required service processor 115 policyand/or profile settings.

In some embodiments, the service usage limits set in the billing system123 service plan record, and/or the service profile record stored in theAAA system 121 can be acquired (e.g., from the apparatus or from adatabase storing the settings for the apparatus) by the servicecontroller (or another network function) and directly translated andused to program the settings in the service processor 123. In someembodiments, the service usage limits are determined or obtained by theactivation server apparatus embodiments, other apparatus embodimentsassociated with service activation, or the virtual service providerembodiments, as described herein. In this manner, once the associationof the service usage profile or policy settings used by a device serviceprocessor 115 and the profile or policy settings used by the variousnetwork apparatus functions is established, then the service policy orprofile for service monitoring, control, billing, verification and/oractions taken on verification error can be coordinated between deviceand network even if some of the network functions act independent ofsome of the device functions.

For example, associating the service usage policies and/or profilesbetween the device service processor 115 and the various networkapparatus functions, and then allowing for independent operation oraction by the various functions in a manner that results in acoordinated outcome, facilitates an overlay of the device assistedservices technology onto existing network equipment in a manner thatresults in reliable and verifiable service enhancements while minimizingthe need for major existing network equipment upgrades.

In some embodiments, the association of the service profile or policysettings used by a device service processor 115 and the service profileor policy settings used by the various network apparatus functions canbe provided by a centralized network function that determines theappropriate settings for the network apparatus and the service processor115 and sets one or more settings to each function. In some embodiments,this networking function is provided by a centralized network managementfunction or service account activation function (e.g., the activationserver apparatus embodiments, one of the other disclosed apparatusembodiments associated with service activation or the virtual serviceprovider apparatus embodiments, as described herein).

In some embodiments, the association of the service profile or policysettings used by a device service processor 115 and the service profileor policy settings used by the various network apparatus functions canbe provided by a network function that by reads, receives, queries,pulls or otherwise obtains the setting used by the service controller122 or the service processor 115. The network function can thendetermine the association of the service profile or policy settings usedby a device service processor 115 and the service profile or policysettings required by the various network apparatus functions beforewriting, transmitting, pushing, or otherwise recording the appropriatesettings required by each of the other network apparatus functions. Insome embodiments, this functionality can be implemented in the servicecontroller (e.g., the policy management server, possibly acting incoordination with another network function or server), which then linksinto the databases used for storing the policy or profile settings forthe other network apparatus.

In some embodiments, once the association is established between servicepolicy or profile settings in the network apparatus and the servicepolicy or profile settings in the service processor 115, then thenetwork based service usage measures (e.g., IPDRs communicated to thebilling system 123, the AAA 121, service controller 122 or other networkfunctions used to verify service usage and/or take actions) used forverification of device 100 service usage versus service policy orprofile can be monitored by the network apparatus (e.g., billing system123 and AAA 121) independent of coordination with the service processor115 and/or independent of the service controller 122. In someembodiments, in addition to independent monitoring and verification ofservice usage versus policy, independent service profile or policyverification error response actions can be taken by the networkapparatus (e.g., suspend, quarantine, SPAN or flag device 100, notifythe user and possibly require acknowledgement, or bill the user accountfor service usage overage) without direct involvement by the serviceprocessor 115 and/or the service controller 122.

Accordingly, the association between service profile and/or servicepolicy that is implemented on the device 100 (e.g., service processor115) and the service profile and/or policy usage limits recorded innetwork apparatus can be associated with one another by one or more ofthe following: (A) implementing a function to read from the networkdatabase (e.g., the billing 123 data base, AAA 121 data base, servicecontroller 122 data base, etc.) and mapping the network profiles and/orpolicies to device 100 (e.g., service processor 115) profiles and/orpolicies; (B) implementing a function that simultaneously sets thedevice profile and/or policy and the network equipment profile and/orpolicy recorded in the appropriate data base records; and (C)implementing a function that reads the profile and/or policy on thedevice 100 (e.g., service processor 115) or the service controller 122and then sets the network equipment profile and/or policy recorded inthe appropriate data base records. This allows for a simplified butcoordinated response to monitoring, controlling and billing for serviceusage, for verifying service usage versus service usage profile orpolicy, and/or initiating or carrying out network actions in response toservice usage versus profile or policy verification errors and/or deviceactions in response to service usage versus profile or policyverification errors.

FIG. 17 is another functional diagram illustrating the device basedservice processor 115 and the service controller 122 in accordance withsome embodiments. FIG. 17 provides for various embodiments as similarlydescribed above with respect to the various embodiments described abovewith respect to FIG. 16, with one of the differences being that theservice controller 122 as shown in FIG. 17 is connected to the accessnetwork and not (directly) connected to the Internet. Accordingly, asshown in FIG. 17, in some embodiments, the service control link 1653 isa communications link between the service controller 122 and the serviceprocessor 115 over the access network 1610.

FIG. 18 is another functional diagram illustrating the device basedservice processor 115 and the service controller 122 in which theservice processor controls the policy implementation for multiple accessnetwork modems and technologies in accordance with some embodiments. Asshown, FIG. 18 provides for various embodiments as similarly describedabove with respect to the various embodiments described above withrespect to FIG. 16, with one of the differences being that the serviceprocessor controls the policy implementation for multiple access networkmodems and technologies. Accordingly, as shown in FIG. 18, in someembodiments, a connection manager 1804, which as shown is in controlplane communication with a modem selection and control 1811, provides acontrol and supervision function for one or more modem drivers or modemsthat connect to an access network. In some embodiments, the modemselection and control 1811 selects the access network connection and isin communication with the modem firewall 1655, and modem drivers, whichas shown include Dial/DSL modem driver 1831, Ethernet modem driver 1815,WPAN modem driver 1814, WLAN modem driver 1813, and WWAN modem driver1812, convert data traffic into modem bus traffic for one or more modemsand are in communication with the modem selection and control 1811.

FIG. 19 is another functional diagram illustrating the service processor115 and the service controller 122 in accordance with some embodiments.As shown in FIG. 19, a stripped down (e.g., reduced set ofagents/components/functionality) embodiment of the service processor 115and the service controller 122 are provided in which service policy isnot adaptive but rather is set by the service controller 122. In thisexample, the agent within the service processor 115 that implementsservice policy is the policy implementation agent 1690. Also, in thisexample, the service controller 122 is similarly stripped down to asimplified configuration (e.g., reduced set ofagents/components/functionality).

Referring to FIG. 19, in some embodiments, many of the service policyimplementation verification and compromise protection techniques aresimilarly provided using these simplified configurations of the serviceprocessor 115 and the service controller 122, as described above withrespect to, for example, FIG. 16. For example, the service controldevice link 1691 and service control server link 1638 can be used fordownloading service policies to the policy implementation agent 1690(but, in some embodiments, cannot perform the heartbeat orauthentication function).

For example, a basic service profile or service policy implementationverification technique for this reduced configuration calls for theaccess control integrity server 1654 to obtain IPDRs from access networkAAA server 1621 (or 121) (e.g., or other network functions as describedherein) and compare the service usage exhibited by device 100 with arange of expected service usage that would be expected if the intendedservice policies were in place on the device. In some embodiments, theaccess control integrity server 1654 initiates or carries out one ormore of the service usage profile or policy verification error responseactions disclosed herein, including, for example, one or more of thefollowing: notify the user of the out of policy or overage condition,require the user to acknowledge the condition and/or acknowledge asubsequent billing event to proceed, bill the user for service overage,suspend the device from the network, quarantine the device, SPAN thedevice, or notify a network manager or device management or errorhandling function.

In some embodiments, a service profile or service policy implementationverification technique for this reduced configuration calls for thebilling system 123 to obtain IPDRs from access network AAA server 1621(or 121) (or other network functions as discussed herein) and comparethe service usage exhibited by device 100 with a range of expectedservice usage that would be expected if the intended service policieswere in place on the device. In some embodiments, the billing system 123initiates or carries out one or more of the service usage profile orpolicy verification error response actions disclosed herein, including,for example, one or more of the following: notify the user of the out ofpolicy or overage condition, require the user to acknowledge thecondition and/or acknowledge a subsequent billing event to proceed, billthe user for service overage, suspend the device from the network,quarantine the device, SPAN the device, or notify a network manager ordevice management or error handling function.

In some embodiments, a service profile or service policy implementationverification technique for this reduced configuration calls for the AAAserver 1621 (or 121) itself to compare the service usage exhibited bydevice 100 with a range of expected service usage that would be expectedif the intended service policies were in place on the device. In someembodiments, the AAA server 1621 (or 121) initiates or carries out oneor more of the service usage profile or policy verification errorresponse actions disclosed herein, including, for example, one or moreof the following: notify the user of the out of policy or overagecondition, require the user to acknowledge the condition and/oracknowledge a subsequent billing event to proceed, bill the user forservice overage, suspend the device from the network, quarantine thedevice, SPAN the device, or notify a network manager or devicemanagement or error handling function.

Accordingly, this approach provides a basic first layer of servicepolicy implementation verification that does not depend on device basedagent behavior for the verification. If the service policy is in errorin a way that violates the expected service policy usage limits, thenthe access control integrity server 1654 will detect this condition andappropriate action can be taken. In some embodiments, if one or moreservice policy integrity verification tests fail, the appropriateresponsive actions can include routing the device to quarantine status,sending an error message to the device or device user interface and thensuspend access for the device, and/or limiting access in some waywithout completely suspending access, as similarly described above. Insome embodiments, if one or more service policy integrity verificationtests fail, the appropriate responsive actions can include loggingexcess service usage above the intended service policy limits andbilling the user for some or all of the excess usage, sending the user anotification and/or acknowledgement response request (possibly includinga simple keystroke acknowledgement, or a password, a biometric signatureor other secure response), and/or limiting access in some way withoutcompletely suspending access, as similarly described above.

In some embodiments, a billing system technique provides anotherverification overlay. For example, the service processor 115 can have aset of service policy implementations (or service profile) that callsfor maintaining service usage within a certain limit, or assisting theuser or network to maintain service usage to that limit. The billingsystem 123 can be implemented in a way to provide a “back stop” to theservice usage controls or limits provided for by the service processor115, so that even if the service processor 115 is compromised, hacked,spoofed or is otherwise in error, the billing system 123 protects theservice provider, “service owner”, carrier, VSP or network operator fromunpaid access beyond the service limits. This can be accomplished, forexample, by assigning a service usage limit within the billing system123 so that if the service processor 115 is compromised and the serviceusage runs over the desired limit, the billing system 123 automaticallycharges the user account for the overage. The billing system 123 canreceive service usage information from the IPDRs that are aggregated inthe network as in the case of a conventional billing system, and becausethese network based measures are independent from the device agentoperation, they cannot be spoofed by merely spoofing something on thedevice or service processor 115. In this manner, defeating the serviceprocessor 115 service agent control mechanisms described herein simplyresults in a billing charge and not free service. In some embodiments,if the service usage runs over the service usage limit specified in theservice profile, the user can be notified as discussed herein, and theuser can be required to acknowledge the overage and approve a billingcharge for the overage as also discussed herein, with theacknowledgement being communicated back to the network in someembodiments. This positive acknowledgement also provides a layer ofprotection and verification of the service control and usage limitcontrol for the device service processor 115. In some embodiment alsodiscussed herein, the user is requested to input a password, biometricor other secure response to the usage overage notification, providingyet another layer of protection to verify that the user intends to payfor the service usage overage. In these embodiments taken individuallyor in combination, the service processor 115 assistance for serviceusage control can be verified and/or protected from compromise.

In some embodiments, the service control device link 1691 and servicecontrol server link 1638 are used to implement the service processor 115heartbeat authentication and communication functions to strengthen theverification of a proper service policy implementation of theembodiments of FIG. 19. For example, the heartbeat function can be usedas authentication for service monitoring versus network reports. Inaddition, the heartbeat function can be used as authentication forchallenge/response queries of agents. Also, the heartbeat function canbe used as authentication for access control. In some embodiments, tostrengthen verification of the basic system illustrated in FIG. 19, thecommunication access to the policy implementation agent 1690 isrestricted so that software or hardware on device 100 and/or on anetwork cannot have authorized access to the policy implementation agent1690. For example, authorized access to the policy implementation agent1690 can be restricted to include only the service controller 122through the service control device link 1691 and the service controlserver link 1638. For example, the agent control bus 1630 can be securedwith encryption and/or other security techniques so that only theservice control device link 1691 can have authorized access to thepolicy implementation agent 1690. As another example, the agent levelmessage encryption can be used as described herein.

In some embodiments, the service policy implementation agent 1690 of theembodiments of FIG. 19 can be further strengthened against errors,intrusion, tampering, hacking and/or other inadvertent or intentionalintegrity degradation by using various other techniques. For example,the dynamic agent download feature of the service controller 122 candownload a new version of the policy implementation agent 1690. In thisexample, the new agent code can be identical in functionality and alsohashed, obfuscated or ordered differently before signing and encryptionso that any hacking attempt must be reinitiated, and this process can beperiodically repeated or repeated upon a triggering event. Additionally,once the new dynamically loaded agent is in place, it can be required toperform an environment scan to determine if the system configuration oroperation are as expected, and/or it can seek to detect elements in theexecution environment that can be harmful or threatening to theintegrity of the policy implementation. The agent can also be requiredto report back on the scan within a relatively short period of time sothat any attempt to compromise the agent does not have sufficient timeto be effective.

In some embodiments, the service policy implementation agent 1690 of theembodiments of FIG. 19 can be further strengthened to protect the policyimplementation from compromise attempts by locating the software and/orhardware used onto an access modem associated with the service. Forexample, the modem can make it difficult to get access to the policyimplementation agent 1690 by employing one or more security elements onone or more access ports into the modem, such as the device bus, an I/Oport, a network connection or the debug port. The modem can also storeand/or execute the policy implementation agent in secure memory. Themodem can also require a secure download key or a secure softwaresignature to accept any updates to the agent software.

In some embodiments, the service policy implementation agent 1690 of theembodiments of FIG. 19 can be further strengthened against compromiseattempts by performing scans of the device 100 code executionenvironment and/or code storage environment to identify potentiallymalicious and/or unwanted/untrusted software or hardware. For example,this function can be performed by the policy implementation agent 1690.The agent can have a local database of potentially malicious elementsand compare the entries in the database against the elements detectedlocally using various malicious code, behavior blocking, intrusiondetection, and/or other well known techniques for security analysis.Alternatively or in addition, the agent can communicate a list of someor all of the elements detected locally to the service controller 122 toaugment or take the place of the database comparison function that canbe performed locally, thereby performing such or further such securityanalysis on the network (e.g., by the service controller 122), and, insome embodiments, if not automatically detected, such elements detectedlocally (e.g., and/or samples of such detected potentially maliciouscode or logs of potentially malicious/suspicious behavior/intrusions)forwarded to security analysts for the service provider for furthersecurity analysis (e.g., service provider security analysts and/or anoutside security vendor engaged to protect the service provider'snetwork and supported devices). In some embodiments, the agent detectsnew software downloads, installs and/or invocations and immediatelyissues an error flag report when potentially malicious software isdownloaded, installed or invoked (e.g., file and network based on accesssecurity detection techniques). In some embodiments, the agent scans thelocal software loading and invocation activity along with a log of othersoftware runtime events and regularly reports this trace so that when anerror or compromise event occurs the trace preceding the event can beanalyzed to determine the offending software or activity trace that tookplace to cause the compromise or error. For example, once the softwareor activity that caused the compromise is known or otherwise detected,it can be entered into a refreshed version of the database that thedevice and other devices use to detect potentially malicious precursorconditions. Examples of such precursor events can include softwareinvocations, software downloads, a sequence of memory I/O events, asequence of software access events, a sequence of network address or URLcommunications or downloads, or a sequence of access modem I/O activity.

FIG. 20 is another functional diagram illustrating the service processor115 and the service controller 122 in accordance with some embodiments.As shown in FIG. 20, the modem firewall 1655 has been removed, andfirewall and access control and traffic shaping functions are performedin these embodiments by the policy implementation agent 1690 andapplication interface agent 1693.

FIG. 21 is another functional diagram illustrating the service processor115 and the service controller 122 in accordance with some embodiments.FIG. 21 illustrates the various modem drivers and modems 2122 through2125 and 2141. In some embodiments, the modems, which include WWAN modem2122, WLAN modem 2123, WPAN modem 2124, Ethernet modem 2125, andDial/DSL modem 2141, which are in communication with the modem bus 2120,connect the device to one or more networks. As shown, the servicemeasurement points labeled I through VI represent various servicemeasurement points for service monitor agent 1696 and/or other agents toperform various service monitoring activities. Each of these measurementpoints can have a useful purpose in various embodiments describedherein. For example, each of the traffic measurement points that isemployed in a given design can be used by a monitoring agent to trackapplication layer traffic through the communication stack to assistpolicy implementation functions, such as the policy implementation agent1690, or, in some embodiments, the modem firewall agent 1655 or theapplication interface agent 1693, in making a determination regardingthe traffic parameters or type once the traffic is farther down in thecommunication stack where it is sometimes difficult or impossible tomake a complete determination of traffic parameters. It should be notedthat although the present invention does not need to implement any orall of the measurement points illustrated in FIG. 21 to have aneffective implementation as was similarly shown with respect to FIG. 19,various embodiments benefit from these and/or similar measurementpoints. It should also be noted that the exact measurement points can bemoved to different locations in the traffic processing stack, just asthe various embodiments described herein can have the agents affectingpolicy implementation moved to different points in the trafficprocessing stack while still maintaining effective operation.

As shown in FIG. 21, measurement point I occurs at the applicationinterface agent 1693 interface to the applications. At this measurementpoint, the application traffic can be monitored before it is framed,packetized or encrypted by the lower layers of the networking stack. Forexample, this allows inspection, characterization, tagging (literal orvirtual) and, in some embodiments, shaping or control of services ortraffic. At this measurement point, traffic can be more readilyassociated with applications, URLs or IP addresses, content type,service type, and other higher level parameters. For example, at thislevel email traffic and downloads, web browser applications and endpoints, media file transfers, application traffic demand, URL trafficdemand and other such service monitoring parameters are more readilyobserved (e.g., accessible in the clear without the need for deep packetinspection and/or decryption), recorded and possibly shaped orcontrolled. As described herein, it is also possible to monitor upstreamtraffic demand at this point and compare it to the other measurementpoints to determine if the traffic policies in place are meeting overalltraffic control policy objectives or to determine if traffic policyimplementation is operating properly. For example, the downstreamdelivered traffic can be optimally observed at this measurement point.

As shown in FIG. 21, traffic measurement points II and III are situatedon the upstream and downstream sides of policy implementation agent1690. As described herein, these two locations allow potential trackingof upstream and downstream traffic through the stack portions associatedwith the policy implementation agent 1690. These two locations alsoprovide for potential cross-checking of how the policy implementationagent 1690 is impacting the demand and delivery of traffic. In a similarmanner, measurement point III in connection with measurement point IVprovide an opportunity for packet tracing through the stack componentsassociated with the modem firewall 1655 and provide for the opportunityto observe the demand and delivery sides of the modem firewall 1655.Traffic measurement point V provides the potential for observing thetraffic at the modem bus drivers for each of the modems.

As shown in FIG. 21, traffic measurement point VI provides, in someembodiments, the ultimate measure of access traffic, for example, thetraffic that actually transacts over the access network through themodem. As shown, measurement point VI is at the modem side of theinternal or external communications bus 1630, and it will be appreciatedthat, in some embodiments, this measurement point can be further downthe modem stack closer to the MAC or physical layer (e.g., at thedesigner's discretion). An advantage of having a measurement point deepin the modem is, for example, that if the software or hardware thatimplements the measurement and reporting is well secured againstcompromise, then this measure can be almost as strong from averification perspective as the measure that comes from the network(e.g., from the network elements). Accordingly, this makes it possibleto compare this measure against the other measures to determine if thereis a traffic path that is leaking past the other measurement point orone or more policy implementation points.

FIG. 22 provides a table summarizing various service processor 115agents (and/or components/functions implemented in software and/orhardware) in accordance with some embodiments. Many of these agents aresimilarly described above, and the table shown in FIG. 22 is notintended to be an exhaustive summary of these agents, nor an exhaustivedescription of all functions that the agents perform or are describedherein, but rather FIG. 22 is provided as a summary aid in understandingthe basic functions of each agent in accordance with some embodimentsand how the agents interact with one another, with the servicecontroller server elements, and/or with other network functions incertain embodiments to form a reliable device based service deliverysolution and/or platform.

FIG. 23 provides a table summarizing various service controller 122server elements (and/or components/functions implemented in softwareand/or hardware) in accordance with some embodiments. Many of theseagents are similarly described above, and the table shown in FIG. 23 isnot intended to be an exhaustive summary of these server elements, noran exhaustive description of all functions that the elements perform orare described herein, but rather FIG. 23 is provided as a summary aid inunderstanding the basic functions of each element in accordance withsome embodiments and how the elements interact with one another, certainnetwork elements, and/or the service processor agents in certainembodiments to form a reliable device based service delivery solutionand/or platform.

In some embodiments, it is desirable to provide a control plane betweenthe service processor and the service controller using a flexibleconnection or communication path that, for example, will work betweenvirtually any two network connection endpoints, one being the servicecontroller and one being the device, in a secure yet scalable manner. Inview of the embodiments described herein, one of ordinary skill in theart will recognize that it is possible to achieve such features with avariety of different embodiments that share similar core features to theembodiments described herein.

Service Control Device Link and Continuous Heartbeat Authentication

As described herein, there are numerous ways to implement the controlplane communication channel between the service processor 115 and theservice controller 122. Various embodiments described herein disclose asecure and bandwidth efficient control plane that is compatible with anyIP based network (including the ability to locate the service controller122 over the Internet); provides for consistent device assisted servicemonitoring, control, verification and/or billing while roaming acrossmultiple networks with different access technologies; and allowscontinuous device assisted service control verification and/orauthentication with a variety of mechanisms for setting the transmissionheartbeat frequency. Other techniques that could be used for thisfunction include, for example, encapsulating the control plane in theaccess network control plane channel, encapsulating the control plane inIP or data packet framing mechanisms (e.g., IPV6), running a moreconventional VPN or IPSEC channel, and/or using an independent accessnetwork connection.

FIG. 24 is a functional diagram illustrating the service control devicelink 1691 of the service processor 115 and the service control servicelink 1638 of the service controller 122 in accordance with someembodiments. In particular, the service control device link 1691 of theservice processor 115 and the service control service link 1638 of theservice controller 122 as shown in FIG. 24 provide for secure controlplane communication over the service control link 1653 between theservice processor 115 and the service controller 122 in accordance withsome embodiments. Various embodiments include two or three layers ofencryption in the service control link, with one embodiment or layerbeing implemented in the encrypt functions (2408, 2428) and decodefunctions (2412, 2422), and another embodiment or layer implemented inthe transport services stack (2410, 2420). An optional third embodimentor layer of encryption is implemented below the transport servicesstack, for example, with IPSEC or another IP layer encryption, VPN ortunneling scheme. For example, various known security encryptiontechniques can be implemented in the encrypt functions (2408, 2428),with public/private or completely private keys and/or signatures so thatvery strong levels of security for service processor control planetraffic can be achieved even through the basic transport services (2410,2420) implemented with standard secure or open Internet networkingprotocols, such as TLS or TCP. For example, the service processor agentcommunications local to the device can be conducted to and from theservice controller elements via the service control device link 1691connection to the agent communication bus 1630. The combination of theservice control device link 1691 and the agent communication bus 1630,which in some embodiments is also securely encrypted or signed, providesa seamless, highly secure, asynchronous control plane connection betweenthe service processor and service controller server elements and theservice controller and service controller agents that works over a widerange of access networks, such as any access network that has thecapability to connect IP or TCP traffic to another TCP or IP endpoint onthe access network, another private network or over the Internet 120. Asdescribed herein, in some embodiments, the agent communication bus 1630also provides a fourth level of encrypted or signed communication toform a secure closed system on the device for agent to agentcommunication, for example, making it very difficult or practicallyimpossible for software or applications to gain access to one or more ofthe a service processor agents on the device in any way other than theservice control device link 1691. In this way, in some embodiments, theagent communication bus 1630 and the service processor agents can onlybe accessed by one another as necessary or permitted by agentcommunication policies, or by the service controller or other authorizednetwork function with proper security credentials communicating over theservice control device link 1691. Additionally, in some embodiments,communications between a subset of two or more agents, or between one ormore agents and one or more service controller server elements areencrypted with unique keys or signatures in such a way that a fourthlevel of security providing private point to point, point to multipoint,or multipoint to multipoint secure communication lines is provided.

In some embodiments, all of the service control device link 1691communications are transformed into a continuous control planeconnection, with a frequency based on the rate of service usage, aminimum set period between connections, and/or other methods forestablishing communication frequency. In some embodiments, thisheartbeat function provides a continuous verification link by which theservice controller verifies that the service processor and/or device areoperating properly with the correct service policies being implemented.In view of the following heartbeat function embodiments describedherein, it will be apparent to one of ordinary skill in the art thatdifferent approaches for implementing the various heartbeat embodimentsare possible, and it will be clear that there are many ways to achievethe essential features enabling a reliable, sometimes continuous controllink and verification function for the purpose of assisting control ofservice usage in a verifiable manner. As shown, inside the serviceprocessor 115, the service control device link 1691 includes a heartbeatsend counter 2402 in communication with the agent communication bus1630. For example, the heartbeat send counter 2402 can provide a countfor triggering when a service processor 115 communication (e.g.,periodic communication based on a heartbeat mechanism) should be sent tothe service controller 122, and a heartbeat buffer 2404, also incommunication with the agent communication bus 1630, buffers any suchinformation for the next service processor 115 communication, inaccordance with various heartbeat based embodiments, as similarlydescribed herein. The heartbeat buffer 2404 is in communication with aframing element 2406 and an encrypt element 2408 for framing andencrypting any service processor 115 communications transmitted to theservice controller 122 by a transport services stack 2410 over theservice control link 1653. Similarly, as shown inside the servicecontroller 122, the service control server link 1638 includes aheartbeat send counter 2434 in communication with a service controllernetwork 2440, a heartbeat buffer 2432, also in communication with theservice controller network 2440, buffers any such information for thenext service controller 122 communication, in accordance with variousheartbeat based embodiments, as similarly described herein. Theheartbeat buffer 2432 is in communication with a framing element 2430and an encrypt element 2428 for framing and encrypting any such servicecontroller 122 communications transmitted to the service processor 115by a transport services stack 2420 over the service control link 1653.

As also shown inside the service processor 115 of FIG. 24, the servicecontrol device link 1691 includes a decode element 2412 for decoding anyreceived service controller 122 communications (e.g., decryptingencrypted communications), an unpack element 2414 for unpacking thereceived service controller 122 communications (e.g., assemblingpacketized communications), and an agent route 2416 for routing thereceived service controller 122 communications (e.g., commands,instructions, heartbeat related information or status reports, policyrelated information or configuration settings and/or updates,challenge/response queries, agent refreshes and/or new software forinstallation) to the appropriate agent of the service processor 115.Similarly, as shown inside the service controller 122, the servicecontrol server link 1638 also includes a decode element 2422 fordecoding any received service processor 115 communications (e.g.,decrypting encrypted communications), an unpack element 2424 forunpacking the received service processor 115 communications (e.g.,assembling packetized communications), and an agent route 2426 forrouting the received service processor 115 communications (e.g.,responses to instructions and/or commands, heartbeat related informationor status reports, policy related information or configuration settingsand/or updates, challenge/response queries, agent status information,network service/cost usage and/or any other reporting relatedinformation) to the appropriate agent of the service controller 122.Accordingly, as described herein with respect to various embodiments,the various secure communications between the service controller 122 andthe service processor 115 can be performed using the embodiment as shownin FIG. 24, and those of ordinary skill in the art will also appreciatethat a variety of other embodiments can be used to similarly provide thevarious secure communications between the service controller 122 and theservice processor 115 (e.g., using different software and/or hardwarearchitectures to provide secure communications, such as using additionaland/or fewer elements/functions or other design choices for providingsuch secure communications).

In some embodiments, an efficient and effective communication framingstructure between the service processor and service controller isprovided, and the following embodiments (e.g., as shown and describedwith respect to FIG. 25) teach such a structure that packs the variousservice processor agent control plane communications and the variousservice controller element control plane connections into a format thatdoes not consume excessive bandwidth to enable a continuous controlplane connection between the device and service controller. In someembodiments, an efficient and effective communication framing structurebetween the service processor and service controller is provided tobuffer such communication messages for some period of time beforeframing and transmitting, such as in a heartbeat frequency that is basedon rate of service usage. In some embodiments, an efficient andeffective communication framing structure between the service processorand service controller is provided to allow for the frame to be easilypacked, encrypted, decoded, unpacked and the messages distributed. Inview of the various embodiments described herein, it will be apparent toone of ordinary skill in the art that many framing structures will workfor the intended purpose of organizing or framing agent communicationsand the uniqueness and importance of combining such a system elementwith the device service controller functions, the service processorfunctions, the service control verification functions and/or the otherpurposes.

FIG. 25 is a functional diagram illustrating a framing structure of aservice processor communication frame 2502 and a service controllercommunication frame 2522 in accordance with some embodiments. Inparticular, the service control device link 1691 of the serviceprocessor 115 and the service control service link 1638 of the servicecontroller 122 (e.g., as shown in FIG. 24) provide for secure controlplane communication over the service control link 1653 between theservice processor 115 and the service controller 122 using communicationframes in the format of the service processor communication frame 2502and the service controller communication frame 2522 as shown in FIG. 25in accordance with some embodiments. As shown, the service processorcommunication frame 2502 includes a service processor framing sequencenumber 2504, a time stamp 2506, an agent first function ID 2508, anagent first function message length 2510, an agent first functionmessage 2512, and assuming more than one message is being transmitted inthis frame, an agent Nth function ID 2514, an agent Nth function messagelength 2516, and an agent Nth function message 2518. Accordingly, theservice processor communication frame 2502 can include one or moremessages as shown in FIG. 25, which can depend on networking framelength requirements and/or other design choices. Similarly, as shown,the service controller communication frame 2522 includes a servicecontroller framing sequence number 2524, a time stamp 2526, an agentfirst function ID 2528, an agent first function message length 2530, anagent first function message 2532, and assuming more than one message isbeing transmitted in this frame, an agent Nth function ID 2534, an agentNth function message length 2536, and an agent Nth function message2538. Accordingly, the service controller communication frame 2522 caninclude one or more messages as shown in FIG. 25, which can depend onnetworking frame length requirements and/or other design choices.

FIGS. 26A through 26E provide tables summarizing various serviceprocessor heartbeat functions and parameters (e.g., implemented byvarious agents, components, and/or functions implemented in softwareand/or hardware) in accordance with some embodiments. Many of theseheartbeat functions and parameters are similarly described above, andthe tables shown in FIGS. 26A-E are not intended to be an exhaustivesummary of these heartbeat functions and parameters, but rather areprovided as an aid in understanding these functions and parameters inaccordance with some heartbeat based embodiments described herein.

FIGS. 27A through 27G provide tables summarizing various device basedservice policy implementation verification techniques in accordance withsome embodiments. Many of these device based service policyimplementation verification techniques are similarly described above,and the tables shown in FIGS. 27A-G are not intended to be an exhaustivesummary of these device based service policy implementation verificationtechniques, but rather are provided as an aid in understanding thesetechniques in accordance with some device based service policyembodiments described herein.

FIGS. 28A through 28C provide tables summarizing various techniques forprotecting the device based service policy from compromise in accordancewith some embodiments. Many of these techniques for protecting thedevice based service policy from compromise are similarly describedabove, and the tables shown in FIGS. 28A-C are not intended to be anexhaustive summary of these techniques for protecting the device basedservice policy from compromise, but rather are provided as an aid inunderstanding these techniques in accordance with some device basedservice policy embodiments described herein.

Device Assisted Service Control and Traffic Control

As described below, various techniques are disclosed for implementingdevice assisted traffic shaping and service control at the lower levelsof service usage policy implementation.

FIG. 29 is a functional diagram illustrating a device communicationsstack that allows for implementing verifiable traffic shaping policy,access control policy and/or service monitoring policy in accordancewith some embodiments. As shown, several service agents take part indata path operations to achieve various data path improvements, and, forexample, several other service agents can manage the policy settings forthe data path service, implement billing for the data path service,manage one or more modem selection and settings for access networkconnection, interface with the user and/or provide service policyimplementation verification. Additionally, in some embodiments, severalagents perform functions to assist in verifying that the service controlor monitoring policies intended to be in place are properly implemented,the service control or monitoring policies are being properly adheredto, that the service processor or one or more service agents areoperating properly, to prevent unintended errors in policyimplementation or control, and/or to prevent tampering with the servicepolicies or control. As shown, the service measurement points labeled Ithrough VI represent various service measurement points for servicemonitor agent 1696 and/or other agents to perform various servicemonitoring activities. Each of these measurement points can have auseful purpose in various embodiments described herein. For example,each of the traffic measurement points that is employed in a givendesign can be used by a monitoring agent to track application layertraffic through the communication stack to assist policy implementationfunctions, such as the policy implementation agent 1690, or in someembodiments the modem firewall agent 1655 or the application interfaceagent 1693, in making a determination regarding the traffic parametersor type once the traffic is farther down in the communication stackwhere it is sometimes difficult or impossible to make a completedetermination of traffic parameters. For example, a detailed set ofembodiments describing how the various measurement points can be used tohelp strengthen the verification of the service control implementationare described herein, including, for example, the embodiments describedwith respect to FIG. 16 and FIG. 21. The particular locations for themeasurement points provided in these figures are intended asinstructional examples, and other measurement points can be used fordifferent embodiments, as will be apparent to one of ordinary skill inthe art in view of the embodiments described herein. Generally, in someembodiments, one or more measurement points within the device can beused to assist in service control verification and/or device or servicetroubleshooting.

In some embodiments, the service monitor agent and/or other agentsimplement virtual traffic tagging by tracking or tracing packet flowsthrough the various communication stack formatting, processing andencryption steps, and providing the virtual tag information to thevarious agents that monitor, control, shape, throttle or otherwiseobserve, manipulate or modify the traffic. This tagging approach isreferred to herein as virtual tagging, because there is not a literaldata flow, traffic flow or packet tag that is attached to flows orpackets, and the book-keeping to tag the packet is done through trackingor tracing the flow or packet through the stack instead. In someembodiments, the application interface and/or other agents identify atraffic flow, associate it with a service usage activity and cause aliteral tag to be attached to the traffic or packets associated with theactivity. This tagging approach is referred to herein as literaltagging. There are various advantages with both the virtual tagging andthe literal tagging approaches. For example, it can be preferable insome embodiments to reduce the inter-agent communication required totrack or trace a packet through the stack processing by assigning aliteral tag so that each flow or packet has its own activity associationembedded in the data. As another example, it can be preferable in someembodiments to re-use portions of standard communication stack softwareor components, enhancing the verifiable traffic control or servicecontrol capabilities of the standard stack by inserting additionalprocessing steps associated with the various service agents andmonitoring points rather than re-writing the entire stack to correctlyprocess literal tagging information, and in such cases, a virtualtagging scheme may be desired. As yet another example, some standardcommunication stacks provide for unused, unspecified or otherwiseavailable bit fields in a packet frame or flow, and these unused,unspecified or otherwise available bit fields can be used to literallytag traffic without the need to re-write all of the standardcommunication stack software, with only the portions of the stack thatare added to enhance the verifiable traffic control or service controlcapabilities of the standard stack needing to decode and use the literaltagging information encapsulated in the available bit fields. In thecase of literal tagging, in some embodiments, the tags are removed priorto passing the packets or flows to the network or to the applicationsutilizing the stack. In some embodiments, the manner in which thevirtual or literal tagging is implemented can be developed into acommunication standard specification so that various device or serviceproduct developers can independently develop the communication stackand/or service processor hardware and/or software in a manner that iscompatible with the service controller specifications and the productsof other device or service product developers.

It will be appreciated that although the implementation/use of any orall of the measurement points illustrated in FIG. 29 is not required tohave an effective implementation, such as was similarly shown withrespect to various embodiments described herein, such as with respect toFIGS. 19 and 21, various embodiments can benefit from these and/orsimilar measurement points. It will also be appreciated that the exactmeasurement points can be moved to different locations in the trafficprocessing stack, just as the various embodiments described herein canhave the agents affecting policy implementation moved to differentpoints in the traffic processing stack while still maintaining effectiveoperation. In some embodiments, one or more measurement points areprovided deeper in the modem stack (e.g., such as for embodimentssimilarly described herein with respect to FIGS. 35 and 36) where, forexample, it is more difficult to circumvent and can be more difficult toaccess for tampering purposes if the modem is designed with the propersoftware and/or hardware security to protect the integrity of the modemstack and measurement point(s).

Referring to FIG. 29, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for each of the modems of thedevice at the bottom of the device communications stack. Examplemeasurement point VI resides within or just above the modem driverlayer. For example, the modem driver performs modem bus communications,data protocol translations, modem control and configuration to interfacethe networking stack traffic to the modem. As shown, measurement pointVI is common to all modem drivers and modems, and it is advantageous forcertain embodiments to differentiate the traffic or service activitytaking place through one modem from that of one or more of the othermodems. In some embodiments, measurement point VI, or anothermeasurement point, is located over, within or below one or more of theindividual modem drivers. The respective modem buses for each modemreside between example measurement points V and VI. In the next higherlayer, a modem selection & control layer for multimode device basedcommunication is provided. In some embodiments, this layer is controlledby a network decision policy that selects the most desirable networkmodem for some or all of the data traffic, and when the most desirablenetwork is not available the policy reverts to the next most desirablenetwork until a connection is established provided that one of thenetworks is available. In some embodiments, certain network traffic,such as verification, control, redundant or secure traffic, is routed toone of the networks even when some or all of the data traffic is routedto another network. This dual routing capability provides for a varietyof enhanced security, enhanced reliability or enhanced manageabilitydevices, services or applications. In the next higher layer, a modemfirewall is provided. For example, the modem firewall provides fortraditional firewall functions, but unlike traditional firewalls, inorder to rely on the firewall for verifiable service usage control, suchas access control and security protection from unwanted networkingtraffic or applications, the various service verification techniques andagents described herein are added to the firewall function to verifycompliance with service policy and prevent tampering of the servicecontrols. In some embodiments, the modem firewall is implemented fartherup the stack, possibly in combination with other layers as indicated inother Figures. In some embodiments, a dedicated firewall function orlayer is provided that is independent of the other processing layers,such as the policy implementation layer, the packet forwarding layerand/or the application layer. In some embodiments, the modem firewall isimplemented farther down the stack, such as within the modem drivers,below the modem drivers, or in the modem itself. Example measurementpoint IV resides between the modem firewall layer and an IP queuing androuting layer. As shown, an IP queuing and routing layer is separatefrom the policy implementation layer where the policy implementationagent implements a portion of the traffic control and/or service usagecontrol policies. As described herein, in some embodiments, thesefunctions are separated so that a standard network stack function can beused for IP queuing and routing, and the modifications necessary toimplement the policy implementation agent functions can be provided in anew layer inserted into the standard stack. In some embodiments, the IPqueuing and routing layer is combined with the traffic or service usagecontrol layer. Examples of this combined functionality are shown anddescribed with respect to FIGS. 31, 32 and 33. For example, a combinedrouting and policy implementation layer embodiment can also be used withthe other embodiments, such as shown in FIG. 29. Various detailedembodiments describing how the policy implementation layer can controltraffic or other service usage activities are described with respect toFIG. 38. Measurement point III resides between the IP queuing androuting layer and a policy implementation agent layer. Measurement pointII resides between the policy implementation agent layer and thetransport layer, including TCP, UDP, and other IP as shown. The sessionlayer resides above the transport layer, which is shown as a socketassignment and session management (e.g., basic TCP setup, TLS/SSL)layer. The network services API (e.g., HTTP, HTTPS, FTP (File TransferProtocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) residesabove the session layer. Measurement point I resides between the networkservices API layer and an application layer, shown as applicationservice interface agent in the device communications stack of FIG. 29.

As shown, the application service interface layer is above the standardnetworking stack API and, in some embodiments, its function is tomonitor and in some cases intercept and process the traffic between theapplications and the standard networking stack API. In some embodiments,the application service interface layer identifies application trafficflows before the application traffic flows are more difficult orpractically impossible to identify farther down in the stack. In someembodiments, the application service interface layer in this way assistsapplication layer tagging in both the virtual and literal tagging cases.In the case of upstream traffic, the application layer tagging isstraight forward, because the traffic originates at the applicationlayer. In some downstream embodiments, where the traffic or serviceactivity classification relies on traffic attributes that are readilyobtainable, such as source address or URL, application socket address,IP destination address, time of day or any other readily obtainedparameter, the traffic type can be identified and tagged for processingby the firewall agent or another agent as it initially arrives. In otherembodiments, as described herein, in the downstream case, the solutionis generally more sophisticated when a traffic parameter that is neededto classify the manner in which the traffic flow is to be controlled orthrottled is not readily available at the lower levels of the stack,such as association with an aspect of an application, type of content,something contained within TLS, IPSEC or other secure format, or otherinformation associated with the traffic. Accordingly, in someembodiments the networking stack identifies the traffic flow before itis fully characterized, categorized or associated with a serviceactivity, and then passes the traffic through to the applicationinterface layer where the final classification is completed. In suchembodiments, the application interface layer then communicates thetraffic flow ID with the proper classification so that after an initialshort traffic burst or time period the policy implementation agents canproperly control the traffic. In some embodiments, there is also apolicy for tagging and setting service control policies for traffic thatcannot be fully identified with all sources of tagging includingapplication layer tagging.

Various applications and/or a user service interface agent communicatevia this communications stack, as shown (illustrating suchcommunications with a reference (A)). Also, the billing agent, which isin communication with the agent communication bus 1630, communicatesuser information and decision query and/or user input to the userservice interface agent, as shown. The policy control agent communicatesservice settings and/or configuration information via thiscommunications bus 1630, as shown (illustrating such communications witha reference (B) via the application layer, policy implementation agentlayer, which is lower in the communications stack as shown, and/or themodem firewall layer). The connection manager agent communicates selectand control commands and/or modem and access network information viathis communications stack, as shown (illustrating such communicationswith a reference (C) via the modem selection and control layer). Variousother communications (e.g., service processor and/or service controllerrelated communications, such as service usage measure information and/orapplication information) are provided at various levels of thiscommunications stack, as shown (illustrating such communications withreferences (D) at the application layer, (E) at the policyimplementation agent layer, and (F) at the modem firewall layer).

As shown in FIG. 29, a service monitor agent, which is also incommunication with the agent communication bus 1630, communicates withvarious layers of the device communications stack. For example, theservice monitor agent, performs monitoring at each of measurement pointsI through VI, receiving information including application information,service usage and other service related information, and assignmentinformation. An access control integrity agent is in communication withthe service monitor agent via the agent communications bus 1630, as alsoshown.

In some embodiments, one or more of the networking stack modificationsdescribed herein in combination one or more of the service verificationand tamper prevention techniques described herein is provided. Assimilarly described with respect to FIG. 29, the various exampleembodiments for assisting service control verification described hereinand as summarized in the example tables provided in FIGS. 26, 27 and 28can be employed individually or in combination to create increasinglysecure cross-functional service control verification embodiments. InFIG. 29, the presence of the access control integrity agent, policycontrol agent, service monitor agent and the other agents that performverification and/or tamper prevention functions illustrates verifiableservice control aspects in accordance with some embodiments.Furthermore, the presence of the billing agent combined with the serviceverification and/or tamper prevention agents and techniques describedherein provides for a set of verifiable billing embodiments for servicebilling, service billing offset corrections, bill by account,transaction billing and other billing functions. In addition, thepresence of the user service interface agent in combination with theservice control agent functions in the modified networking stack providefor embodiments involving a combination of service control with userpreferences, which as described herein, provides the user with thecapability to optimize service versus service cost in a network neutralmanner. In some embodiments, the user control of service control policyis provided along with the service control verification and/or tamperprevention. The presence of the policy control agent that in someembodiments implements a higher than most basic level of policy decisionand control with the policy implementation agents in the modifiednetworking stack allows for, for example, the device to possess thecapability to implement a higher level of service control for thepurpose of obtaining a higher level service usage or service activityobjective. In some embodiments, the application layer tagging incombination with other embodiments described herein provides for deepservice activity control that is verifiable.

In some embodiments, verifiable traffic shaping as described herein canbe performed using the device communications stack in a variety ofembodiments for the combination of service control within the networkingstack and service control verification and/or tamper prevention, withvarious embodiments depicted in FIGS. 29 through 37. Additional levelsof detail regarding how such embodiments can be used to implementverifiable traffic shaping are provided in and described with respect toFIGS. 38 through 40 which depict example functional diagrams of packetprocessing flows for verifiable traffic shaping or service activitycontrol in a device service processor for both upstream and downstreamflows. Along with several other interesting features embodied in FIGS.38 through 40, application traffic layer tagging is depicted inadditional detail in accordance with some embodiments. For example, theapplication interface agent can determine service data usage at theapplication layer using measurement point I and a local service usagecounter, and can, for example, pass this information to the servicemonitor agent. If service usage exceeds a threshold, or if using aservice usage prediction algorithm results in predicted service usagethat will exceed a threshold, then the user can be notified of whichapplications are causing the service usage overrun or potential serviceusage overrun, via the user service interface agent. The user can thenidentify which application service (e.g., traffic associated with aspecified high service use or non-critical application, such as forexample a high bandwidth consumption social networking website orservice, media streaming website or service, or any other high bandwidthwebsite or service transmitting and/or receiving data with the servicenetwork) that the user prefers to throttle. As another example, the usercould select a service policy that allows for video chat services untilthose services threaten to cause cost over-runs on the user's serviceplan, and at that time the service policy could switch the chat serviceto voice only and not transmit or receive the video. The trafficassociated with the user specified application can then be throttledaccording to user preference input. For example, for downstream traffic,packets (e.g., packets that are virtually or literally tagged and/orotherwise associated with the application traffic to be throttled) fromthe access network can be buffered, delayed and/or dropped to throttlethe identified application traffic. For upstream traffic, packets (e.g.,packets that are virtually or literally tagged and/or otherwiseassociated with the application traffic to be throttled) can bebuffered, delayed and/or dropped before being transmitted to the accessnetwork to throttle the identified application traffic. As similarlydescribed above, traffic shaping as described herein can be verified,such as by the service monitor agent via the various measurement pointsand/or using other agents.

The embodiments depicted in FIG. 30 and other figures generally requireenhancements to conventional device networking communication stackprocessing. For example, these enhancements can be implemented in wholeor in part in the kernel space for the device OS, in whole or in part inthe application space for the device, or partially in kernel space andpartially in application space. As described herein, the networkingstack enhancements and the other elements of the service processor canbe packaged into a set of software that is pre-tested or documented toenable device manufacturers to quickly implement and bring to market theservice processor functionality in a manner that is compatible with theservice controller and the applicable access network(s). For example,the service processor software can also be specified in aninteroperability standard so that various manufacturers and softwaredevelopers can develop service processor implementations orenhancements, or service controller implementations or enhancements thatare compatible with one another.

FIG. 30 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In some embodiments, a portion of theservice processor is implemented on the modem (e.g., on modem modulehardware or modem chipset) and a portion of the service processor isimplemented on the device application processor subsystem. It will beapparent to one of ordinary skill in the art that variations of theembodiment depicted in FIG. 30 are possible where more or less of theservice processor functionality is moved onto the modem subsystem oronto the device application processor subsystem. For example, suchembodiments similar to that depicted in FIG. 30 can be motivated by theadvantages of containing some or all of the service processor networkcommunication stack processing and/or some or all of the other serviceagent functions on the modem subsystem (e.g., and such an approach canbe applied to one or more modems). For example, the service processorcan be distributed as a standard feature set contained in a modemchipset hardware of software package or modem module hardware orsoftware package, and such a configuration can provide for easieradoption or development by device OEMs, a higher level ofdifferentiation for the chipset or modem module manufacturer, higherlevels of performance or service usage control implementation integrityor security, specification or interoperability standardization, and/orother benefits.

Referring to FIG. 30, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for modem MAC/PHY layer at thebottom of the device communications stack. Measurement point IV residesabove the modem MAC/PHY layer. The modem firewall layer resides betweenmeasurement points IV and III. In the next higher layer, the policyimplementation agent is provided, in which the policy implementationagent is implemented on the modem (e.g., on modem hardware). Measurementpoint II resides between the policy implementation agent and the modemdriver layer, which is then shown below a modem bus layer. The nexthigher layer is shown as the IP queuing and routing layer, followed bythe transport layer, including TCP, UDP, and other IP as shown. Thesession layer resides above the transport layer, which is shown as asocket assignment and session management (e.g., basic TCP setup,TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (FileTransfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS)resides above the session layer. Measurement point I resides between thenetwork services API layer and an application layer, shown asapplication service interface agent in the device communications stackof FIG. 30.

Various applications and/or a user service interface agent communicatevia this communications stack, as shown (illustrating suchcommunications with a reference (A)). Also, the billing agent, which isin communication with the agent communication bus 1630 communicationsuser information and decision query and/or user input to the userservice interface agent, as shown. The policy control agent Bcommunicates service settings and/or configuration information via thiscommunications stack, as shown (illustrating such communications with areference (B)) via the application layer. The policy control agent Acommunicates service settings and/or configuration information via thiscommunications stack, as shown (illustrating such communications with areference (D)) via the policy implementation agent layer and/or themodem firewall layer. The connection manager agent communicates select &control commands and/or modem and access network information via thiscommunications stack, as shown (illustrating such communications with areference (C)) via the modem driver layer. Various other communications(e.g., service processor and/or service controller relatedcommunications, such as service usage measure information, and/orapplication information) are provided at various levels of thiscommunications stack, as shown (illustrating such communications withreferences (E)) at the application layer through the modem driver layerwith the service monitor agent B as shown (and an access controlintegrity agent B is also shown), and communications with references (F)at the policy implementation agent layer and (G) at the modem firewalllayer with the service monitor agent A as shown (and an access controlintegrity agent A is also shown). In some embodiments, the service usagepolicy verification or tamper prevention embodiments described hereincan be applied, in isolation or in combination, in the context of FIG.31 to provide for embodiments with increasing levels of service usagepolicy control verification certainty, such as provided with FIGS. 26,27 and 28.

FIG. 31 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In some embodiments, the serviceprocessor is a simplified implementation. For example, this approach canbe used for applications with less capable device applicationprocessors, rapid time to market needs, fewer service usage controlneeds, and/or other reasons that lead to a need for a lower complexityimplementation.

Referring to FIG. 31, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for the modem layer at the bottomof the device communications stack. The modem driver layer resides abovethe modem bus layer as shown. In the next higher layer, the policyimplementation agent is provided, and the policy implementation agent isalso in communication with the agent communication bus 1630 as shown.The next higher layer is shown as the transport layer, including TCP,UDP, and other IP as shown. The session layer resides above thetransport layer, which is shown as a socket assignment and sessionmanagement (e.g., basic TCP setup, TLS/SSL) layer. The network servicesAPI (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple MailTransfer Protocol), POP3, DNS) resides above the session layer.Applications communicate with the device communications stack via thenetwork services API as shown. Policy settings from the network (e.g.,service settings) are communicated with the policy implementation agentas shown. The connection manager communicates select and control as wellas modem and access network information via the modem driver as shown.Although FIG. 31 does not depict all of the service usage controlverification functions provided by certain embodiments calling foradditional service verification or control agents, a high level ofservice policy implementation verification certainty can be achievedwithin the context of the embodiments depicted in FIG. 31 by applying asubset of the service usage policy verification or tamper preventionembodiments described herein. For example, the embodiments depicted inFIG. 31 can be combined with the service controller embodiments thatutilize IPDRs to verify service usage is in accordance with the desiredservice policy. There are also many other service usage controlembodiments described herein that can be applied in isolation or incombination to the embodiments depicted in FIG. 31 to provide increasinglevels of service usage control verification certainty, as will beapparent to one of ordinary skill in the art in view of FIGS. 26, 27 and28 and the various embodiments described herein.

FIG. 32 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In some embodiments, the serviceprocessor is a simplified implementation embodiment with device basedmonitoring and integrity control. For example, FIG. 32 provides forsomewhat higher complexity (e.g., relative to the embodiments depictedin FIG. 30) in exchange for the enhanced service monitoring, control orverification that are possible by implement additional agentembodiments, such as the service monitor agent and the access controlintegrity agent functions.

Referring to FIG. 32, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for each of the modems of thedevice at the bottom of the device communications stack. Measurementpoint II resides above the modem selection & control layer, whichresides above the modem buses for each modem. Measurement point Iresides between the policy implementation agent (policy basedrouter/firewall) layer and the transport layer, including TCP, UDP, andother IP as shown. The session layer resides above the transport layer,which is shown as a socket assignment and session management (e.g.,basic TCP setup, TLS/SSL) layer. The network services API (e.g., HTTP,HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail TransferProtocol), POP3, DNS) resides above the session layer. Applicationscommunicate with the device communications stack via the networkservices API as shown. Policy settings from the network (e.g., servicesettings) are communicated with the policy implementation agent asshown. The connection manager communicates select and control as well asmodem and access network information via the modem selection and controllayer as shown. The service monitor agent, which is also incommunication with the agent communication bus 1630, communicates withvarious layers of the device communications stack. For example, theservice monitor agent, performs monitoring at each of measurement pointsI and II, receiving information including application information,service usage and other service related information, and assignmentinformation. An access control integrity agent is in communication withthe service monitor agent via the agent communications bus 1630, as alsoshown. As similarly described with respect to FIGS. 30 and 31, many ofthe service usage control verification embodiments described herein canbe applied in isolation or in combination in the context of FIG. 32.

FIG. 33 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. Referring to FIG. 33, describing thedevice communications stack from the bottom to the top of the stack asshown, the device communications stack provides a communication layerfor each of the modems of the device at the bottom of the devicecommunications stack. Measurement point III resides above the modemselection & control layer, which resides above the, respective modembuses for each modem. Measurement point II resides between the policyimplementation agent (policy based router/firewall) layer and thetransport layer, including TCP, UDP, and other IP as shown. The sessionlayer resides above the transport layer, which is shown as a socketassignment and session management (e.g., basic TCP setup, TLS/SSL)layer. The network services API (e.g., HTTP, HTTPS, FTP (File TransferProtocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) residesabove the session layer. Measurement point I resides between the networkservices API layer and an application layer, shown as applicationservice interface agent in the device communications stack of FIG. 33.

Various applications and/or a user service interface agent communicatevia this communications stack, as shown (illustrating suchcommunications with a reference (A)). Also, the billing agent, which isin communication with the agent communication bus 1630 communicationsuser information and decision query and/or user input to the userservice interface agent, as shown. The policy control agent communicatesservice settings and/or configuration information via thiscommunications stack, as shown (illustrating such communications with areference (B)) via the policy implementation agent layer. The connectionmanager agent communicates select & control commands and/or modem andaccess network information via this communications stack, as shown(illustrating such communications with a reference (C)) via the modemselection and control layer. Various other communications (e.g., serviceprocessor and/or service controller related communications, such asservice usage measure information, application information) are providedat various levels of this communications stack, as shown (illustratingsuch communications with references (D)) at the application layer and(E) at the policy implementation agent layer.

As shown in FIG. 33, a service monitor agent, which is also incommunication with the agent communication bus 1630, communicates withvarious layers of the device communications stack. For example, theservice monitor agent, performs monitoring at each of measurement pointsI through III, receiving information including application information,service usage and other service related information, and assignmentinformation. An access control integrity agent is in communication withthe service monitor agent via the agent communications bus 1630, as alsoshown. As similarly described with respect to FIGS. 30, 31 and 32, manyof the service usage control verification embodiments disclosed hereincan be applied in isolation or in combination in the context of FIG. 33.

FIG. 34 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In some embodiments, the data pathprocessing for the service processor is provided in conjunction with asingle modem driver as shown. As shown, the service processorcommunication stack processing is provided below the standard networkcommunication stack and in combination with a modem driver (e.g., andthis approach can be extended to more than one modem).

Referring to FIG. 34, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for each of the modems of thedevice at the bottom of the device communications stack. Measurementpoint II resides above the modem driver 1 layer. Measurement point Iresides between the policy implementation agent (policy basedrouter/firewall) layer and the modem selection and control layer, forthe modem driver 1 stack in this single modem driver embodiment. Thetransport layer, including TCP, UDP, and other IP resides above the IPqueuing and routing layer, which resides above the modem selection andcontrol layer, as shown. The session layer, which is shown as a socketassignment and session management (e.g., basic TCP setup, TLS/SSL)layer, resides above the transport layer. The network services API(e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple MailTransfer Protocol), POP3, DNS) resides above the session layer.

As shown in FIG. 34, applications communicate with the devicecommunications stack via the network services API as shown (illustratingsuch communications with a reference (A)). Policy settings from thenetwork (e.g., service settings) are communicated with the policyimplementation agent as shown (illustrating such communications with areference (B)). The service monitor agent, which is also incommunication with the agent communication bus 1630, communicates withpolicy implementation agent layer of the device communications stack.Also, the service monitor agent performs monitoring at each ofmeasurement points I and II, receiving information including applicationinformation, service usage and other service related information, andassignment information. An access control integrity agent is incommunication with the service monitor agent via the agentcommunications bus 1630, as also shown. Various other communications(e.g., service processor and/or service controller relatedcommunications, such as service usage measure information, applicationinformation) are provided at various levels of this communicationsstack, as shown (illustrating such communications with references (C))at the policy implementation agent layer. Also, the billing agent, whichis in communication with the agent communication bus 1630 communicationsuser information and decision query and/or user input to the userservice interface agent, as shown. As similarly described with respectto FIGS. 30, 31, 32 and 33, many of the service usage controlverification embodiments disclosed herein can be applied in isolation orin combination in the context of FIG. 34.

FIG. 35 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In particular, FIG. 35 illustrates asingle modem hardware embodiment as shown. As shown, the serviceprocessor network communication stack processing is provided on themodem hardware (e.g., and this approach can be extended to more than onemodem). This approach allows for the service processor to be distributedas a standard feature set contained in a modem chipset hardware ofsoftware package or modem module hardware or software package, which,for example, can provide for easier adoption or development by deviceOEMs, a higher level of differentiation for the chipset or modem modulemanufacturer, higher levels of performance or service usage controlimplementation integrity, or other benefits.

Referring to FIG. 35, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for each of the modems of thedevice at the bottom of the device communications stack. As shown,measurement points I and II and the policy implementation agent resideon the modem 1 (e.g., implemented as hardware and/or software on modem1). Measurement point I resides above the policy implementation agent(policy based router/firewall) layer, and measurement point II residesbelow the policy implementation agent later. The modem selection andcontrol layer resides above the modem drivers layer, as shown. Thetransport layer, including TCP, UDP, and other IP resides above the IPqueuing and routing layer, which resides above the modem selection andcontrol layer, as shown. The session layer, which is shown as a socketassignment and session management (e.g., basic TCP setup, TLS/SSL)layer, resides above the transport layer. The network services API(e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple MailTransfer Protocol), POP3, DNS) resides above the session layer.

As shown in FIG. 35, applications communicate with the devicecommunications stack via the network services API as shown. Policysettings from the network (e.g., service settings) are communicated withthe policy implementation agent as shown (illustrating suchcommunications with a reference (A)). The service monitor agent, whichis also in communication with the agent communication bus 1630,communicates with policy implementation agent layer of the modem 1.Also, the service monitor agent performs monitoring at each ofmeasurement points I and II, receiving information including applicationinformation, service usage and other service related information, andassignment information. An access control integrity agent is incommunication with the service monitor agent via the agentcommunications bus 1630, as also shown. Various other communications(e.g., service processor and/or service controller relatedcommunications, such as service usage measure information and/orapplication information) are provided at various levels of thiscommunications stack, as shown (illustrating such communications withreferences (B)) at the policy implementation agent layer. As similarlydescribed with respect to FIGS. 30, 31, 32, 33 and 34, many of theservice usage control verification embodiments disclosed herein can beapplied in isolation or in combination in the context of FIG. 35.

FIG. 36 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In particular, FIG. 36 illustrates asingle modem hardware embodiment, in which modem 1 includes a portion ofthe service processor networking communication stack processing andmeasurement points II and III and the policy implementation agent, assimilarly shown in FIG. 35, and the higher levels of the devicecommunications stack above the modem 1 layer, such as the applicationservice interface layer, are implemented on the device applicationprocessor or in the device application processor memory as similarlydescribed above, for example, with respect to FIG. 33, in which ameasurement point I is shown between the application service interfaceagent layer and the network services API layer. For example, thisapproach allows for the application service interface agent to beprovided on the device application processor or memory so thatapplication layer service usage monitoring or control can beimplemented. For example, the differences between the embodimentsdepicted in FIG. 36 and those of FIG. 30 include a simplifiedimplementation and a policy control agent that is entirely implementedon the modem and not partially implemented in the application processormemory.

Various applications and/or a user service interface agent communicatevia this communications stack, as shown (illustrating suchcommunications with a reference (A)). Also, the billing agent, which isin communication with the agent communication bus 1630 communicationsuser information and decision query and/or user input to the userservice interface agent, as shown. The policy control agent communicatesservice settings and/or configuration information via thiscommunications stack, as shown (illustrating such communications with areference (B)) via the policy implementation agent layer. Various othercommunications (e.g., service processor and/or service controllerrelated communications, such as service usage measure information and/orapplication information) are provided at various levels of thiscommunications stack, as shown (illustrating such communications withreference (C) at the application layer and communications with reference(D) at the policy implementation agent layer). As shown, the servicemonitor agent B communicates with the application service interfaceagent and measurement point I, and the service monitor agent Acommunicates with the policy implementation agent layer and measurementpoints II and III of the modem 1. As similarly described with respect toFIGS. 30, 31, 32, 33, 34 and 35, many of the service usage controlverification embodiments disclosed herein can be applied in isolation orin combination in the context of FIG. 36.

FIG. 37 is another functional diagram illustrating the devicecommunications stack that allows for implementing traffic shapingpolicy, access control policy and/or service monitoring policy inaccordance with some embodiments. In particular, FIG. 37 illustrates adevice communications stack as similarly shown in FIG. 36, with thedifference being that the service processor subsystem networkingcommunication stack processing is implemented on a hardware functionthat is separate from the application processor and the modem. Forexample, this approach provides security advantages with a dedicatedhardware system to protect some or all of the service usage controlsystem from tampering. For example, some or all of the service processorcan be implemented on a SIM card module. As another example, some or allof the service processor can be encapsulated on a self containedhardware module that can be added to a device without the need to modifythe networking communication stack software or hardware.

FIG. 38 is a functional diagram illustrating a device service processorpacket processing flow in accordance with some embodiments. Inparticular, both an example upstream service processor packet processingflow (device to the network) and an example downstream service processorpacket processing flow (network to the device) are shown in FIG. 38. Forexample, the service processor packet processing flow can be performedby the device communications stack, such as described above with respectto FIG. 29. The various embodiments for packet processing flow depictedin FIGS. 38 through 40 are self explanatory to one of ordinary skill inthe art and not all the processing steps and flow sequences aredescribed herein.

In some embodiments, the burst size, buffer delay, acknowledgement delayand drop rate used in upstream and downstream traffic shaping areoptimized with the goal of reducing access network traffic overhead, andexcess capacity usage that can result from mismatches in traffictransmission parameters with the access network MAC and PHY or fromexcess network level packet delivery protocol re-transmissions. In someembodiments, an application interface agent 1693 is used to literallytag or virtually tag application layer traffic so that the policyimplementation agent(s) 1690 has the necessary information to implementselected traffic shaping solutions. As shown in FIG. 16, the applicationinterface agent 1693 is in communication with various applications,including a TCP application 1604, an IP application 1605, and a voiceapplication 1602.

Referring to FIGS. 38 through 40, in some embodiments, the upstreamtraffic service policy implementation step corresponds to the trafficshaping step described herein. Referring to FIG. 38, this step isdepicted as shown as an alternate exploded view including four upstreamsub-steps of apply QoS queue priority, apply traffic shaping rules,network optimized buffer/delay and remove application ID tag. Anadditional approach shown in FIG. 38 involves two exploded viewsub-steps associated with the firewall service policy implementationstep and these sub-steps are pass/block packet and pass/redirect packet.For example, the functions performed by these six sub-steps can bedepicted in any number of sub-steps, the order of the steps can beappropriately performed in various different orders to provide forupstream traffic shaping within the network communication stack. Forexample, FIGS. 39 and 40 show the two steps of policy implementation andfirewall as one step and the six exploded view sub-steps are includedunder the same policy implementation step and are performed in adifferent order than in FIG. 38. It should also be noted that a numberof embodiments are possible in which the access control, traffic controlor firewall functions are moved to the application service interfacelayer or another layer.

Referring now to the downstream portion of FIG. 38, there are two stepsagain termed traffic service policy implementation and firewall servicepolicy implementation in this traffic shaping, access control andfirewall example. These two packet flow processing steps are depicted asshown in the exploded view as the five sub-steps of tag with flow ID,pass/block packet, apply QoS, apply traffic shaping rules and networkoptimized buffer, delay, and drop. As with the upstream packetprocessing flow, the number of sub-steps, the order of sub-steps and thelocation of the sub-steps in the downstream networking stack processingcan be depicted in any number of sub-steps, order and/or location, andvarious other embodiments will be apparent to one of ordinary skill inthe art, including embodiments which locate some or all of the steps inthe application service interface layer or other layers as depicted inFIGS. 39 and 40. The details of the packet flow processing design forthe downstream can be somewhat more complex in certain embodiments ascompared to the upstream processing in two ways. First, as describedherein, in some embodiments, the packet tagging that requiresapplication level information can require the initial portion of thepacket flow burst to pass through the upstream networking communicationstack until the application service interface layer can associate thepacket flow with the appropriate information visible at the applicationlevel at which time the packet flow tag is communicated to the otherservice processor agent functions so that they can properly monitor orcontrol the traffic associated with the flow.

Independently, another complication arises when upper layer reliablecommunication protocols, such as TCP, are employed in the networkingstack in which the downstream transmitting end repeats the packettransmission if the receiving TCP protocol stack does not send a packetreceipt acknowledge (ACK) within a certain period of time. If packetsare arbitrarily delayed or dropped, then the TCP re-transmission trafficcan reduce, completely eliminate or even reverse the network capacityadvantage gained by reducing the average traffic speed or othertransmission quality measure for one or more service activities. Tosolve this problem, in some embodiments, the packet traffic controlparameters (e.g., downstream delay, drops, burst length, burst frequencyand/or burst jitter) are optimized for TCP re-transmission efficiency sothat changes in traffic control access bandwidth or speed for one ormore service activities are implemented in such a manner that the TCPre-transmission delay at the network transmitting end adapts to be longenough so that wasted packet re-transmission bandwidth is reduced. Inaddition, and either in combination or in isolation, in someembodiments, the packet traffic control parameters (e.g., downstreamdelay, drops, burst length, burst frequency and/or burst jitter) can beadjusted so that the access network downstream MAC and/or PHYefficiencies are optimized.

Numerous other embodiments for the detailed implementation of packetflow processing in both downstream and upstream will be apparent to oneof ordinary skill in the art in view of the various embodimentsdescribed herein. In some embodiments, as described herein, thefollowing are provided: (A) traffic shaping is performed in a verifiablemanner, (B) traffic shaping is performed in a manner that results inimproved network capacity by taking into account to some degree themanner in which the access network PHY layer and/or MAC layer respondsto packet parameters (e.g. burst delay, burst drops, burst length, burstfrequency and/or burst jitter), (C) traffic shaping is performed in amanner that results in improved network capacity by taking into accounthow the packet parameters (e.g., burst delay, burst drops, burst length,burst frequency and/or burst jitter) impact layer 3 and higher ACKprotocol or other network protocol network capacity efficiencies, (D)packet shaping is performed in a manner that is aware of and optimizedfor the particular type of communication protocol or packets being sent(e.g., TCP packets can be dropped to slow the application rate oftransfer whereas UDP packets are never dropped, because there is nore-transmission), (E) a virtual or literal packet tagging system is usedin a verifiable traffic shaping service control system to provide adeeper level of service monitoring and control or to simplify theprocessing of the packets, and/or (F) starting with these low levelpacket processing, traffic control or access control building blocks oneor more additional layers of higher level policy control can be added onthe device or in the network to create service profiles for the serviceprovider network that define complete services, such as ambient servicesand many other variations of service profile settings that each define adevice or user service experience and can be associated with a billingplan. For example, the use of higher layers of service profile controlto form more complete service solutions starting with these relativelysimple low-level traffic control, access control or firewall processingsteps or functions is also described herein.

FIG. 39 is another functional diagram illustrating the device serviceprocessor packet processing flow in accordance with some embodiments. Inparticular, both an example upstream service processor packet processingflow (device to the network) and an example downstream service processorpacket processing flow (network to the device) are shown in FIG. 39(e.g., of a less feature rich device service processor embodiment, suchas one similar to that depicted in FIG. 32).

FIG. 40 is another functional diagram illustrating the device serviceprocessor packet processing flow in accordance with some embodiments. Inparticular, both an example upstream service processor packet processingflow (device to the network) and an example downstream service processorpacket processing flow (network to the device) are shown in FIG. 40(e.g., of a mid=-featured embodiment of a device service processor, suchas one similar to that depicted in FIG. 33).

FIG. 41 provides a table summarizing various privacy levels for servicehistory reporting in accordance with some embodiments. Many of theseprivacy levels are similarly described above, and the table shown inFIG. 41 is not intended to be an exhaustive summary of these privacylevels, but rather is provided as an aid in understanding these privacylevels in accordance with user privacy related embodiments describedherein. For example, there are many other parameters that can beassociated with privacy filtering, and as will be apparent to one ofordinary skill in the art in view of the various embodiments describedherein, the unique feature of user defined or user influenced privacyfiltering for service usage, service activity or CRM reports can beimplemented with a variety of embodiments that are variations of thosedescribed herein.

FIGS. 42A through 42F provide tables summarizing various service policycontrol commands in accordance with some embodiments. Many of theseservice policy control commands are similarly described above, and thetables shown in FIGS. 42A-F are not intended to be an exhaustive summaryof these service policy control commands and do not include summaries ofall the embodiments described herein, but rather are provided as asummary aid in understanding these service policy control commands inaccordance with various embodiments described herein.

In some embodiments, QoS is employed for devices with a serviceprocessor 115. For example, QoS can be employed in a crowded hot spotwhere the service processor 115 profile has been changed from WWAN toWLAN, but the WLAN is backed up as too many users are trying to use it.The service processor 115 can have a hierarchical access to the hotspotat that point; or the service processor 115 that pays less can bethrottled while those that pay more are opened up; or the serviceprocessor 115 can initiate a policy that slows down transmissions toimprove trunking efficiency.

FIGS. 43A through 43B are flow diagrams illustrating a flow diagram fora service processor authorization sequence as shown in FIG. 43A and aflow diagram for a service controller authorization sequence as shown inFIG. 43B in accordance with some embodiments.

Referring to FIG. 43A, at 4302, the device is in an offline state. At4304, the service processor (e.g., service processor 115) of the devicecollects device service processor credentials and access controlintegrity information. At 4306, the service processor of the deviceselects a best network. At 4308, the device connects to an accessnetwork. At 4310, the service processor of the device sends anauthorization request to the service controller (e.g., servicecontroller 122) and also sends the credentials and access controlintegrity information. At 4312, the service processor determines whetheran integrity error has occurred. If so, then the service processorperforms integrity error handling at 4314. Otherwise, the serviceprocessor determines whether the device is activated and/or authorizedfor network access at 4316. If not, then the service processor performsa device activation sequence at 4318. At 4320, the service processorperforms the following: updates critical software, initializes servicepolicy and control settings, synchronizes service counters, updatesservice cost data, applies policy settings, applies CRM rules settings,obtains transaction identity certificate, and sends stored CRM andbilling information. At 4322, the device is in an online state.

Referring to FIG. 43B, at 4332, device control is in an offline state.At 4334, the service controller (e.g., service controller 122) receivesa device authorization request, verifies device service plan standing,verifies device access control integrity standing, verifies deviceaccess control integrity information, verifies service processorheartbeat, and performs various additional service processor integritychecks (e.g., as similarly described herein). At 4336, the servicecontroller determines whether the device integrity checks have allpassed. If not, then the service controller sends an integrity error tothe service processor (e.g., service processor 115) at 4338. At 4340,the service controller performs integrity error handling. Otherwise (thedevice integrity checks have all passed), the service controllerdetermines whether the device is activated at 4342. If not, then theservice controller sends an activation message to the service processorat 4344. At 4346, the service controller performs a service activationsequence. Otherwise (the device is activated), the service controllersends an authorization at 4348. At 4350, the service controller performsthe following: updates critical software on the service processor,initializes service policy and control settings, synchronizes servicecounters, updates service cost data, applies policy settings, appliesCRM rules settings, obtains transaction identity certificate, sendsstored CRM and billing information. At 4352, the service controller isin a device online state.

FIGS. 44A through 44B are flow diagrams illustrating a flow diagram fora service processor activation sequence as shown in FIG. 44A and a flowdiagram for a service controller activation sequence as shown in FIG.44B in accordance with some embodiments.

Referring to FIG. 44A, at 4402, a service processor activation sequenceis initiated. At 4404, the service processor (e.g., service processor115) of the device displays an activation site (e.g., HTTP site, WAPsite or portal) to the user for the user's service activation choice. At4406, the user selects service plan, billing information and CRMinformation. At 4408, the service processor sends an activation requestand user billing and CRM information to, for example, the servicecontroller. At 4410, the service processor determines whether there isan integrity error. If so, then the service processor performs integrityerror handling at 4412. Otherwise, the service processor determineswhether there has been a selection input error at 4414. If so, theservice processor displays the selection input error to the user at 4416and returns to the activation site/portal at 4404. Otherwise, theservice processor identifies the activated service plan at 4418. At4420, the service processor performs the following: updates criticalsoftware, initializes service policy and control settings, synchronizesservice counters, updates service cost data, applies policy settings,applies CRM rules settings, obtains transaction identity certificate,and sends stored CRM and billing information. At 4422, the device is inan online and activated state.

Referring to FIG. 44B, at 4432, a service controller activation sequenceis initiated. At 4434, the service controller (e.g., service controller122) receives an activation request, including user billing and CRMinformation, and sends such to central billing. At 4436, the servicecontroller receives a response from central billing. At 4438, theservice controller verifies the integrity of the service processor. Ifan integrity error is detected, then an integrity error is sent at 4440.At 4442, the service controller performs integrity error handling. At4444, the service controller determines whether the service plan hasbeen activated. If not, then the service controller sends a selectioninput error to the device at 4446 and returns to 4432. Otherwise (devicehas been activated), the service controller sends the service planactivation information to the device at 4448. At 4450, the servicecontroller performs the following: updates critical software,initializes service policy and control settings, synchronizes servicecounters, updates service cost data, applies policy settings, appliesCRM rules settings, obtains transaction identity certificate, and sendsstored CRM and billing information. At 4452, the service controller isin a device online and activated state.

FIGS. 45A through 45B are flow diagrams illustrating a flow diagram fora service processor access control sequence as shown in FIG. 45A and aflow diagram for a service controller access control sequence as shownin FIG. 45B in accordance with some embodiments.

Referring to FIG. 45A, at 4502, the device is in an online state. At4504, the service processor (e.g., service processor 115) of the deviceprocesses any new heartbeat messages received from the servicecontroller (e.g., service controller 122). At 4506, the serviceprocessor updates software if necessary, updates service policy andcontrol settings if necessary, synchronizes service counters, updatesservice cost data if necessary, and updates CRM rules if necessary. At4508, the service processor performs access control integrity checks. At4510, the service processor determines whether there are any accesscontrol integrity errors. If so, then the service processor performsintegrity error handling at 4512. Otherwise, the service processorupdates user service UI gauges, provides notification if necessary, andaccepts input if available at 4514. At 4516, the service processor sendsnew service processor heartbeat messages to the heartbeat message queue.At 4518, the service processor processes any pending billingtransactions. At 4520, the service processor determines if a heartbeattransmission is due, and if not, returns to 4504 for processing anyreceived heartbeat messages. If so, at 4522, the service processor sendsthe new service processor heartbeat message to the service controller.

Referring to FIG. 45B, at 4532, the device is in an online state. At4534, the service controller (e.g., service controller 122) processesany new heartbeat messages received from the service processor. At 4536,the service controller performs access control integrity checks. At4538, the service controller determines whether there are any accesscontrol integrity errors. If so, then the service controller performsintegrity error handling at 4540. At 4542, the service controllerupdates the billing database, updates the CRM information, synchronizesservice counters, updates cost database if needed, and synchronizes CRMrules if necessary. At 4544, the service controller processes anypending billing transactions. At 4546, the service controller sends newservice processor heartbeat messages to the heartbeat message queue. At4548, the service controller determines if a heartbeat transmission isdue, and if not, returns to 4534 for processing any received heartbeatmessages. If so, at 4550, the service controller sends new serviceprocessor heartbeat message to the service processor.

Open Content Distribution and Transaction System

Referring now to FIGS. 46 and 47A-B, in another set of embodiments anopen, decentralized, device based system for enabling central billingfor third party electronic commerce transactions for mobile commerce isprovided as shown. For example, in these embodiments, device informationcan be embedded in HTTP, WAP or other portal browser/network headerrequest information that indicates a central billing option is availableto a compatible third party transaction server, as further describedbelow with respect to FIGS. 46 and 47A-B.

FIG. 46 is a functional diagram illustrating open, decentralized, devicebased mobile commerce transactions in accordance with some embodiments.As shown, a service processor 4615 of the device 100 (e.g., any mobiledevice capable of storing and executing the service processor 4615)includes access control integrity agent 1694, billing agent 1695, agentcommunication bus 1630, user interface 1697, policy control agent 1692,service monitor agent 1696, application interface agent 1693, policyimplementation agent 1690, and modem router and firewall 1655, assimilarly described herein with respect to various other serviceprocessor embodiments. In some embodiments, an application 4604 (e.g.,an HTML/WAP web browser) and a mobile payment agent 4699 are alsoincluded in the device, such as part of the service processor 4615 asshown. In some embodiments, the application 4604 is not integrated aspart of the service processor 4615, but is executing and/or stored onthe device. In some embodiments, the mobile payment agent 4699 includesbilling agent 1695, user interface 1697 and/or application interfaceagent 1693, and/or various other functional components/agents. As shown,the service processor 4615 is in communication with a carrier accessnetwork 4610, which is in network communication with the Internet 120.

In some embodiments, device information can be embedded in HTTP, WAP orother portal browser/network header request information that indicates acentral billing option is available to a compatible third partytransaction server, such as the open content transaction partner site(s)134. For example, the compatible transaction server can then send asigned confirmation request over a pre-assigned control socket channelto the billing agent 1695 with the billing agent 1695 confirming thesigned confirmation request by either performing the signature checklocally based on a stored and synchronized list of approved transactionservers or by passing the signed request onto a billing server 4630 forconfirmation. Optionally, in another example, a triangle confirmationcan be set up in which the billing server 4630 can confirm thetransaction set up with the transaction server 134 or the transactionserver 134 can confirm the transaction set up with the billing server4630. Once the device confirms the compatible and approved status of thetransaction server 134, the device/transaction server pair can thenoptionally further exchange keys for the remainder of the transactionfor enhanced security. In another example, the transaction server 134can also redirect the user browsing experience to one tailored to one ormore of device type, service provider, device manufacturer or user. Whenthe user selects a transaction, the transaction server sends the billingagent 1695 a transaction bill that describes the transaction and theamount. The billing agent 1695 can optionally confirm that the useraccount has sufficient credit limit to make the purchase by eitherconfirming the stored credit limit on the device or querying the billingserver 4630. The billing agent 1695 then invokes the device UI 1697 todisplay the transaction description and amount and request user approvalfor the billing to be conducted through the central billing option. Userapproval can be acquired, for example, by a simple click operation orrequire a secure password, key and/or biometric response from the user.Upon user approval, the billing agent 1695 generates a billing approvaland sends it to the transaction server 134, the transaction server 134completes the transaction and then sends a bill to the billing agent1695. The billing agent 1695 optionally sends a confirmation to thetransaction server 134 and sends the bill to the billing server 4630.Again, optionally a triangle confirmation can be formed by the billingserver sending a confirmation to the transaction server 134, or thetransaction server 134 can send the bill to the billing server 4630. Insome embodiments, the billing server 4630 can also communication suchbilled transactions to a central provider billing system 4623 via thecarrier access network 4610. Also, in some embodiments, an alternatelocation billing server 4632 is in communication via the Internet 120,and an alternate location central provider billing system 4625 is alsoin communication via the Internet 120.

FIGS. 47A through 47B are transactional diagrams illustrating open,decentralized, device based mobile commerce transactions in accordancewith some embodiments. Referring to FIG. 47A, the device application4604 browses (e.g., based on the user submitting a browse request usinga browser application) to transaction server 134 (e.g., a transactionweb server, such as the open content transaction partner site 134). Thetransaction server 134 provides an offer to the device application 4604.The device application 4604 selects a purchase (e.g., based on theuser's selection input). In response, the transaction server 134 seeksan API connection with the device mobile payment agent 4699, which thenconfirms the API connection. The transaction server 134 requests userpurchase confirmation (mediated by the device mobile agent 4699 asshown), and the purchase is confirmed by the device application 4604(e.g., based on the user's acknowledgement as similarly described abovewith respect to FIG. 46). The transaction server 134 then transmits apurchase receipt, and the device application 4604 confirms the receipt.The transaction server 134 then transmits the purchase bill to thedevice mobile payment agent 4699, which then sends the purchase bill tothe device billing server (e.g., billing server 4630). The transactionserver also optionally sends a confirmation of the purchase bill to thedevice billing server for a triangle confirmation, as similarlydescribed above with respect to FIG. 46. The device billing server sendsa copy of the purchase bill to the central provider billing system(e.g., central provider billing system 4623).

Referring now to FIG. 47B, the device application 4604 browses (e.g.,based on the user submitting a browse request using a browserapplication) to transaction server 134 (e.g., a transaction web server,such as the open content transaction partner site 134), in which thebrowse request includes device ID information, such as similarlydescribed above with respect to FIG. 46. The transaction server 134establishes API contact with the device mobile agent 4699, which thenconfirms contact and good standing for transactional purchases from thedevice. The transaction server 134 provides an offer to the deviceapplication 4604. The device application 4604 selects a purchase (e.g.,based on the user's selection input). The transaction server 134notifies the device mobile payment agent 4699 of the purchasedescription and amount, and the device mobile payment agent 4699 thenrequests user purchase confirmation. The purchase is confirmed by thedevice application 4604 (e.g., based on the user's acknowledgement assimilarly described above with respect to FIG. 46), and the devicemobile payment agent 4699 then transmits a purchase confirmation to thetransaction server 134. The transaction server 134 then transmits apurchase receipt, and the device application 4604 confirms the receipt.The transaction server 134 then transmits the purchase bill to thedevice mobile payment agent 4699, which then sends the purchase bill tothe device billing server (e.g., billing server 4630). The transactionserver also optionally sends a confirmation of the purchase bill to thedevice billing server for a triangle confirmation, as similarlydescribed above with respect to FIG. 46. The device billing server sendsthe purchase bill to the central provider billing system (e.g., centralprovider billing system 4623). In some embodiments, the communicationsdescribed above with respect to FIGS. 47A-B with the billing server andthe central provider billing system are with the alternate locationbilling server 4632 and/or alternate location central provider billingsystem 4625 via the Internet 120. Similarly, in some embodiments, thetransaction servers 134 are connected to the Internet 120.

Accordingly, these transaction billing embodiments do not requirecentralized content storage or content and transaction exchangeinfrastructure. For example, the transactions can be conducted over theInternet, and the user experience and content can be tailored versionsof the transaction server/content provider's normal experience andcontent. This approach provides for a much wider array of content andtransaction partners with minimal or no need to accommodate proprietaryspecialized systems. Moreover, the compatibility between the devicebilling agent transaction system and the transaction provider server iseasily established, for example, by writing specifications for theheader information transmitted by the device and for the securehandshake and signed message transactions that take place between thedevice billing agent, the transaction server and optionally thetransaction server and the billing server. Once a transaction partnershows compatibility test results and concludes a business relationshipwith the service provider, the service provider can place thetransaction partner on the compatible and approved list and exchangesecurity keys and/or certificates. If a common user experience isdesired by the service provider across multiple transaction partners,then the experience specifications for the browser redirects can also bespecified in the compatibility specification and tested before thetransaction partner gains approval.

Design and Testing for Service Control

FIG. 48 illustrates a network architecture including a servicecontroller device control system and a service controller analysis andmanagement system in accordance with some embodiments. As describedherein, the RAN gateway 410 generally represents the functionality ofthe various specific RAN gateway functional elements shown and/ordiscussed herein. For example, these RAN gateway 410 functional elementsrepresent the gateways used to aggregate the radio access networktraffic, control, charging and roaming functions and/or other functionsand are shown and/or discussed herein using other terminology specificto certain industry standards, including SGSN gateway 410 and gateways508, 512, 608, 612, 708 and 712. Although the same reference numeralsare used for SGSN gateway 410 and RAN gateway 410, it will beappreciated that the RAN gateway 410 represents any or all of the RANgateway functional elements 410, 508, 512, 608, 612, 708, 712 or anyother similar industry equipment or functions depending on theembodiment. Similarly, transport gateway 420 represents the next higherlevel of gateway aggregation for the transport layer that is used inmany networks, and this term transport gateway 420 can be interchangedwith any or all of the gateways 420, 520, 620, 720 or any other similarindustry equipment or functions depending on the embodiment. Those ofordinary skill in the art will appreciate which gateway descriptionapplies to a respective embodiment in which the terms RAN gateway 410,gateway 410, transport gateway 420 or gateway 420 are referenced herein.

While the embodiments described below with respect to FIGS. 48 through63 are depicted in the context of a conventional multi-tier accessnetwork, one of ordinary skill in the art will appreciate that suchembodiments can also be generalized to other network topologiesincluding the various flattened network topologies described herein. Asshown, the service controller is divided into two main functions (e.g.,as compared with the embodiments of service controller 122 depicted inFIG. 16): (1) a service controller device control system 4825 and (2) aservice controller design, policy analysis, definition, test, publishingsystem 4835. The service controller device control system 4825 performsthe device service control channel functions as previously describedherein with respect to various embodiments.

The service controller design, policy analysis, definition, test,publishing system 4835 separates out the service analysis, controlpolicy design and publishing from the device service control channelfunctions. The service controller design, policy analysis, definition,test, publishing system 4835 performs a variety of functions asdescribed below. In some embodiments, the service controller design,policy analysis, definition, test, publishing system 4835 providesservice usage statistical analysis, notification policy or procedureresponse analysis and/or billing policy or procedure response analysisfor single devices, groups of devices, types of devices, groups ofusers, classes of users, or an entire set of devices and users thatsubscribe to a given service. In some embodiments, the servicecontroller design, policy analysis, definition, test, publishing system4835 detects, singles out and reports device service usage, notificationresponses or billing behavior that is outside of expected limits but mayor may not be violating policy. In some embodiments, the servicecontroller design, policy analysis, definition, test, publishing system4835 provides service cost and profitability analysis for singledevices, groups of devices, types of devices, groups of users, classesof users, or an entire set of devices and users that subscribe to agiven service. In some embodiments, the service controller design,policy analysis, definition, test, publishing system 4835 provides userservice control policy, notification policy or billing policystatistical satisfaction analysis for single devices, groups of devices,types of devices, groups of users, classes of users, or an entire set ofdevices and users that subscribe to a given service. In someembodiments, the service controller design, policy analysis, definition,test, publishing system 4835 provides statistical take rate analysis fortransaction offers and billing offers for single devices, groups ofdevices, types of devices, groups of users, classes of users, or anentire set of devices and users that subscribe to a given service.

In some embodiments, the service controller design, policy analysis,definition, test, publishing system 4835 provides service control policydefinition work screens and “dry-lab” (pre-beta) testing against usagedatabase for single devices, groups of devices, types of devices, groupsof users, classes of users, or an entire set of devices and users thatsubscribe to a given service. In some embodiments, the servicecontroller design, policy analysis, definition, test, publishing system4835 provides service control policy, notification policy and/or billingpolicy beta testing (e.g., using beta test server 1658) in which thebeta test profile is published to a subset of users or devices. In someembodiments, beta devices/users may or may not know that the servicepolicy is being tested with them. In some embodiments, if they do know,then beta test apparatus includes offering system that provides useroptions to accept beta test and provide feedback in exchange for anoffer (e.g., show them an offer page that comes up with their existingsubscription service or ambient service—offer a free trial, a discountto something and/or reward zone points (or other incentives/rewards) ifthey accept the trial). In some embodiments, a beta test workstation(e.g., in communication with the beta test server 1658, such as VSPremote workstation 4920 as shown in FIG. 49) allows the beta testmanager to define one or more beta test service policy, notificationpolicy and/or billing policy control profiles. In some embodiments, thebeta test workstation publishes each profile to specific individual(single) devices, groups of devices, types of devices, groups of users,classes of users, or an entire set of devices and users that subscribeto a given service. In some embodiments, the beta test workstationallows the beta test manager to analyze usage statistics, notificationresponse statistics and/or billing/transaction offer response statisticsfor devices, users, groups of devices or groups of users and compareactual real-time usage versus beta test usage goals. In someembodiments, the beta test workstation allows the beta test manager tofine tune service, notification and/or billing/transaction policies andre-publish to observe changes to actual service usage until the servicepolicy and/or notification control policies achieve the desired result.In some embodiments, the beta test workstation also allows the beta testmanager to collect direct user feedback to a set of pre-designed usersatisfaction or other questions regarding service usage. For example,questions can be presented through a pre-designed beta test portal orthrough a series of brief pop-ups that come up when the user initiates aparticular action or at a particular time. In some embodiments, the betatest workstation also collects details of service and device usage(e.g., CRM data) that the beta test users have approved for collection.In some embodiments, the beta test workstation can decompose this datato determine if the users are using the service in the manner intendedby the beta test goals. In some embodiments, the beta test workstationalso allows for publishing multiple variants of the service and/ornotification policy control settings and compare the service usage foreach group with convenient screens with information displays (e.g.,statistical usage versus time of day, usage of particular activities,billing activity, device discovery activity, user response tonotification message and options, user satisfaction with a particularnotification policy or billing policy or traffic control policy). Insome embodiments, the screens can be designed by the beta test manager.

In some embodiments, once a service is completely tested and approvedfor production publication, the service download control server 1660 hasa workstation screen that allows the service manager to specify whichgroup of devices are to receive the new service policy configuration. Insome embodiments, the service download control server 1660 allows theservice manager to define specific individual (single) devices, groupsof devices, types of devices, groups of users, classes of users, or anentire set of devices and users that subscribe to a given service.

In some embodiments, a service (e.g., a newly created or new version ofan existing service) is tested and/or enhanced using a new servicetesting model. For example, a new service (or a new version of anexisting service) is loaded onto a server for testing, the new serviceis (optionally) tested against existing device usage statistics, a newservice control definition (e.g., implemented as service processor 115for publishing to devices 100 and a corresponding new service controller122 for the service provider, such as a central provider or an MVNOpartner, and, for example, the new service processor and servicecontroller can be implemented using the below described SDK) for the newservice is developed and possibly adjusted based on the testing againstexisting device usage statistics, the new service control definition isthen published to beta devices (e.g., various devices 100 used for betatesting the new service), which then use the new service, service usagestatistics and/or user feedback statistics are then collected (e.g., toensure that the service is functioning properly and so that the servicecontrol definition can be tuned to ensure adequate service, userexperience and for service pricing/profitability purposes), theservice/service control definition is then fine tuned based on theservice usage/user feedback statistics. Upon completion of the abovetesting and refinement of the service/service control definition, theservice control definition can be published to specified groups ofdevices for using the new service. In some embodiments, this servicecontrol testing model for groups of devices and service partners isprovided by a virtual MVNO or VSP. For example, this allows for newservices to be more efficiently and more effectively developed, testedand proliferated.

In some embodiments, service history IPDRs come from within a networkingcomponent connected to the central provider core network 110 as depictedby (e.g., real-time) service usage 118 (which as discussed elsewhere isa general purpose descriptor for a function located in one or more ofthe networking equipment boxes). In some embodiments, service historyIPDRs are collected/aggregated (in part) from the central billing system123. In some embodiments, service history IPDRs are collected/aggregated(in part) from the transport gateways 420. In some embodiments, servicehistory IPDRs are collected/aggregated (in part) from the RAN gateways410. In some embodiments, service history IPDRs are collected/aggregated(in part) from the base station(s) 125 or a networking componentco-located with the base station(s) 125, a networking component in thetransport network 415, a networking component in the core network 110 orfrom another source.

Virtual Service Provider for Service Control

In some embodiments, virtual service provider (VSP) capabilities includemaking available to a third party service partner one or more of thefollowing: (1) device group definition, control and security, (2)provisioning definition and execution, (3) ATS activation owner, (4)service profile definitions, (5) activation and ambient servicedefinition, (6) billing rules definition, (7) billing process andbranding controls, (8) bill by account settings, (9) service usageanalysis capabilities by device, sub-group or group, (10) beta testpublishing capabilities by device, sub-group or group, and (11)production publishing, fine tuning and re-publishing.

FIG. 49 illustrates a network architecture for an open developerplatform for virtual service provider (VSP) partitioning in accordancewith some embodiments. As shown, the service controller design, policyanalysis, definition, test, publishing system 4835 is configured so thatmultiple “service group owners” (e.g., the service provider for certainsmart phones) or “device group owners” (e.g., eReader devices for theeReader service provider(s)) or “user group owners” (e.g., IT forCompany X for their employees' corporate mobile devices), collectivelyreferred to as the “Virtual Service Provider” (VSP), are serviced withthe same service controller infrastructure and the same (orsubstantially similar) service processor design from virtual serviceprovider workstation server 4910 and/or virtual service provider remoteworkstation(s) 4920. As shown, the virtual service provider remoteworkstation(s) 4920 communicates with the virtual service providerworkstation server 4910 via VPN, leased line or secure Internetconnections. The dashed lines shown in FIG. 49 are depicted to representthat, in some embodiments, the virtual service provider workstationserver 4910 is networked with the service controller device controlsystem 4825 and/or, in some embodiments, the service controller design,policy analysis, definition, test, publishing system 4835. Based on thediscussion herein, it will be apparent to one of ordinary skill in theart that the VSP workstation server 4910 can also be networked invarious embodiments with billing system 123, AAA server 121, gateways410 or 420, or other network components to perform, for example, variousnetwork provisioning and activation related functions discussed hereinfor the device group assigned to one or more VSPs, or for other reasonsas will be apparent to a given VSP embodiment.

In some embodiments, the service controller functionality is partitionedfor a VSP by setting up one or more secure workstations, secure portals,secure websites, secure remote software terminals and/or other similartechniques to allow the service managers who work for the VSP toanalyze, fine tune, control or define the services they decide topublish to one or more groups of devices or groups of users that the VSP“owns,” In some embodiments, the VSP “owns” such groups by virtue of arelationship with the central provider in which the VSP is responsiblefor the service design and profitability. In some embodiments, thecentral provider receives payment from the VSP for wholesale accessservices. In some embodiments, the VSP workstations 4910 and 4920 onlyhave access to the service analysis, design, beta testing and publishingfunctions for the devices or users “owned” by the VSP. In someembodiments, the user or device base serviced by the central providernetwork is securely partitioned into those owned by the centralprovider, those owned by the VSP, and those owned by any other VSPs.

In some embodiments, the VSP manages their devices from the VSPworkstations 4910 and 4920 using device based service control techniquesas described herein. In some embodiments, the VSP manages their devicesfrom the VSP workstations 4910 and 4920 using device assisted andnetwork based service control techniques as described herein. In someembodiments, the VSP manages their devices from the VSP workstations4910 and 4920 using network based service control techniques (e.g., DPItechniques) as described herein.

For example, this approach is particularly well suited for “opendeveloper programs” offered by the central providers in which thecentral provider brings in VSPs who offer special value in the devicesor service plans, and using this approach, neither the central providernor the VSP needs to do as much work as would be required to set up aconventional MVNO or MVNE system, which often requires some degree ofcustomization in the network solution, the billing solution or thedevice solution for each new device application and/or serviceapplication that is developed and deployed. In some embodiments, theservice customization is simplified by implementing custom policysettings on the service processor and service controller, and the customdevice is quickly brought onto the network using the SDK andtest/certification process. In some embodiments, the VSP functionalityis also offered by an entity other than the central provider. Forexample, an MVNE entity can develop a wholesale relationship with one ormore carriers, use the service controller to create the VSPcapabilities, and then offer VSP services for one network or for a groupof networks. In some embodiments, the service customization issimplified by implementing custom policy settings through the VSPembodiments on the network equipment, including, in some embodiments,service aware or DPI based network equipment that has a relatively deeplevel of service activity control capability. For example, using theembodiments described herein, and possibly also including some of theactivation and provisioning embodiments, it is possible to efficientlydesign and implement custom ambient service plans that are different fordifferent types of devices, different OEMs, different VSPs, differentdistributors, or different user groups all using the same generalinfrastructure, whether the service control policy implementation isaccomplished primarily (or exclusively) with networking equipment(network) based service control, primarily (or exclusively) with devicebased service control or with a combination of both (e.g., hybrid deviceand network based service control).

As discussed herein, various VSP embodiments for performing one or moreof analyzing traffic usage and defining, managing service profiles orplans, dry lab testing service profiles or plans, beta testing serviceprofiles or plans, fine tuning service profiles or plans, publishingservice profiles or plans, or other policy related settings can involveprogramming settings in the network equipment and/or programmingsettings or software on the device. For example, as discussed herein,the service processor settings are controlled by the service controller,which can be partitioned to allow groups of devices to be controlled. Asanother example, equipment in the network involved with network basedservice control, such as DPI based gateways, routers or switches, cansimilarly be programmed to utilize various VSP embodiments to implementthat portion of the service profile (or service activity usage control)that is controlled by network level functions, and it will beappreciated that substantially all or all of the service activitycontrol for certain embodiments can be accomplished with the networkfunctions instead of the device. Continuing this example, just as thedevice service processor settings control functions of the serviceprocessor can have a group of devices that are partitioned off andplaced under the control of a VSP, various VSP control embodiments canpartition off a group of devices that have service usage activitycontrolled by the networking equipment, including, in some embodiments,sophisticated service aware DPI based service control equipment, toachieve similar objectives. It will be appreciated that the discussionherein regarding service controller design, policy analysis, test,publishing 4835, and the discussion regarding device group, user groupand other VSP related embodiments, should be understood as applicable tovarious embodiments described in view of device based services control,control assistance and/or monitoring, or network based services control,control assistance and/or monitoring, or a combination of device basedservices control, control assistance and/or monitoring and network basedservices control, control assistance and/or monitoring. The variousembodiments described herein related to service activation andprovisioning also make apparent how the programming of network equipmentservice control, service control assistance and/or monitoring can beimplemented prior to and following activation of the device. It willalso be appreciated that the VSP capabilities described herein can alsobe applied to those devices that have services controlled by, providedby and/or billed by the central provider, so these techniques can beapplied to central provider service embodiments, MVNO embodiments andother embodiments.

Open Development System for Access Services—SDK

In some embodiments, an SDK is provided that allows developers, such asdevice manufacturers, service providers, MVNO, MVNE and/or VSPs, todevelop various service processors (e.g., different versions of theservice processor 115) for various devices (e.g., various types ofdevices 100) and corresponding service controllers (e.g., differentversions of the service controller 122) for various types of servicesand network environments. For example, a device manufacturer can use theSDK to develop a new service processor for their new device (e.g.,mobile phone, PDA, eBook reader, portable music device, computer,laptop, netbook, or any other network accessible device). The devicemanufacturer can also preload/preinstall their new service processor ontheir new devices. In this example, users of the new device would thenbe able to utilize the new device to access network based services usingthe new service processor, which communicates with the deployed newservice controller, as similarly discussed herein in variousembodiments. For example, the device can be preinstalled with the newservice processor to provide ambient services, as similarly discussedherein in various embodiments. For example, the SDK can allow forsubstantially similar service processors to be installed on similarand/or different devices thereby minimizing any unnecessary differencesbetween service processor elements for device assisted services. In someembodiments, for ambient services for a group of devices, or devicesassociated with a certain service provider, a set of numbers (e.g.,dummy numbers) can be assigned for use for attempting access via theaccess network using a new device that is not yet otherwise subscribedfor service. In some embodiments, the set of (dummy) numbers used forambient access by the device can also be used for associate of thedevice with a service provider or a type of device (e.g., eReader orsome other type of network accessible device), and upon activation, theservice provider assigns a real number for the activated device (e.g.,which can be provided at the time of manufacture of the device, point ofsale of the device, or after the point of sale of the device, such asupon activation of the device). For example, ambient access of thedevice can use the device ID, SIM ID, assigned phone (real or dummy)number, and/or other information associated with the device forassigning appropriate service control and service policy/profile for thedevice.

In some embodiments, the service processor 115 is distributed as an SDKto any device that the central provider or the VSP desires to offerservices with so that the service processor 115 can be efficientlydesigned or adapted by the device OEM, ODM or manufacturer for operationon the service network. In some embodiments, the SDK includes either acomplete set of service processor 115 agent software designed for and/ortested for the OS (Operating System) and processor set being used on thedevice, or a mature reference design for the OS and processor set beingused on the device, or a less mature reference design (potentially forthe same OS and/or processor set or a different OS and/or processor setbeing used on the device) that the OEM (Original Equipment Manufacturer)ports to the desired OS or processor set, or a basic set of examplesoftware programs that the OEM or ODM (Original Design Manufacturer) canuse to develop software compatible with the service, or a set ofspecifications and descriptions (possibly forming an interoperabilitystandard) of how to design the software to be compatible with theservice. In some embodiments, the SDK includes a set of OEM lab testprocedures and/or test criteria to ensure that the implementation of theservice SDK is compatible with the service and will operate properly. Insome embodiments, the SDK includes a set of network certification testprocedures and/or test criteria to ensure that the implementation of theservice SDK is compatible with the service and will operate properly. Insome embodiments, the certification procedures are approved for testingby the OEM, the central provider, the VSP and/or a trusted third party.For example, the central provider is typically in control of the SDK andthe test procedures, but others can be in control. In some embodiments,the test procedures are at least in part common across multiple centralprovider networks. In some embodiments, the SDK concept is extended toinclude one or more modem modules where one or more of the SDKembodiments described above is combined with a standard reference designor a standard hardware sales package for one or more modems so that theentire package forms a turn-key product that allows a devicemanufacturer, central provider, VSP or other entity bring new devices ordevice applications onto the central provider network possibly incombination with other networks in a manner that requires lessengineering time and resources and less network certification time andresources than would be required in some designs that do not use thisstandard SDK plus module approach. For example, the standard SDK plusmodule product embodiments can be pre-certified and tested with one ormore central providers to further reduce development time and expense.The standard SDK plus module embodiments can also use a multi-mode modem(e.g., modems based on a multimode CDMA, EVDO, UMTS, HSPA chipset as inthe Gobi global multimode chipset product or modems based on otherrecently announced LTE plus HSPA chipsets, WiMax plus Wi-Fi chipsets orLTE plus EVDO chipsets) and a multi-mode connection manager agent sothat the same SDK plus modem embodiment may satisfy a wide range ofapplications for many service providers around the world.

In some embodiments, at the time of manufacture, the device isassociated with an MVNO. For example, the MVNO can provide an ambientservice that provides a service provider clearing house, in which thedevice can access a network in ambient access mode (e.g., a wholesaleMVNO connection through the access network) for purposes of selecting aservice provider (e.g., a VSP, MVNO or carrier). Based on the serviceprovider selection, the device credentials and/or service processor arereprogrammed and/or new software is downloaded/installed to activate thedevice with the selected service provider, as described herein forprovisioning the device and the account on that service provider network(e.g., the ATS can track such activation, for example, for revenuesharing purposes, as an activation incentive fee).

In some embodiments ATS is implemented entirely in the network asdescribed below. At the time of manufacture or at sometime during devicedistribution, the device master agent programs a unique credential inthe device that cannot be re-programmed or removed (or is difficult tore-program or remove) and that can be recognized and recorded by thenetwork at the time of activation or at some other time. In this manner,even if other, possibly primary, device credentials are reprogrammed orremoved, there will still be a credential that is associated with thedevice master agent. The ATS process can then be implemented by using adatabase search function to scan through the database of activateddevices to form a list of devices that have been activated for thepurpose of master agent reconciliation. Example credentials that cansuffice are MEID, hardware MAC address, and/or serial number, that arepicked up and recorded by the service provider or other service entityat time of activation or before or after activation.

Interface Server Overlay for Billing/IPDR Feed Mediation

FIG. 50 illustrates a network architecture including a billing toservice controller interface for accommodating minimum changes inexisting central billing, AAA and/or other network components inaccordance with some embodiments. As shown, the central billing system123 includes a mediation, customer service and billing databases,historical usage, billing systems component 5010 and a billing toservice controller interface component 5020. For example, the billing toservice controller interface component 5020 allows for the centralbilling system 123 to efficiently communicate with the servicecontroller (e.g., service controller device control system 4825).

In some embodiments, an interface server (e.g., the billing databases,historical usage, billing systems component 5010 and/or the billing toservice controller interface component 5020) is provided that reads theIPDRs, service profile and/or service plan information stored in thebilling and/or service record database(s). In some embodiments, theinterface server performs these functions in a manner that is compatiblewith communication formats of the billing and/or service recorddatabase(s) so that little or no changes are required in theconfiguration, communication formats or software of the existing centralbilling, AAA and/or other network components. In some embodiments, theinterface server (e.g., including the billing databases, historicalusage, billing systems component 5010 and the billing to servicecontroller interface component 5020) is co-located with the centralbilling system components as shown, or in other embodiments, theinterface server is located elsewhere. For example, the interface servercan be located close to or within the components that comprise theservice controller or anywhere else in the network.

In some embodiments, the interface server performs certain communicationprotocol translation or data format translation required to interfacethe information stored in the billing and/or service record database(s)to the service controller functions so that the central billing system123 and other existing components in the network do not need to changemuch (if at all) to enable the service controller and service processorto implement device based/assisted service control. In some embodiments,the central billing system 123 or other network components are notrequired to be aware of the service control functions being implementedby the service controller or service processor, because the interfaceserver acquires the network based information needed by the servicecontroller and/or service processor while requiring little or nospecialized awareness, communication, data formatting, user interfacing,service profile processing or service plan processing on the part ofexisting billing, database or networking components. In this type ofoverlay approach, various embodiments described herein can be used toquickly upgrade the capabilities of existing networks for new deviceswhile minimizing the required changes to the existing network thatsupports legacy devices.

For example, a new ambient service plan can be implemented within thecentral billing system 123 that is associated with a zero or low costbilling plan and a usage limit (e.g., ambient service) that may bedifficult or impossible to support in a manner that would result in highuser satisfaction and a high level of control for service cost andservice policy definition. Even if the central billing system 123 is nothighly involved in the process, the zero or low cost plan can beimplemented in a manner that results in high user satisfaction and acost controlled service by using the service controller and/or serviceprocessor and the interface server to implement the ambient servicesaccess control, service usage control, user interface, service usagenotification, transaction billing or bill by account functionality. Forexample, this approach can be implemented by reading the service planand/or service policy settings for a device in the central billingdatabase using the interface server, looking up the correspondingservice policy, user notification policy, transaction billing policy andbill by account policy associated with the particular service profile orservice plan, and then implementing the policies with the assistance ofthe service controller and/or service processor. Similarly, in anotherdefinition, multiple tiers of service control and user notificationpolicies can be added to any number of new service profiles or serviceplans that would not otherwise be supported with the central billingsystem 123 and other network components, all with minimal or nomodifications to the pre-existing network and billing system.

Another embodiment calls for receiving a standard IPDR feed from centralbilling 123 or another network component just like an MVNO would. Forexample, the interface server function can be located in the centralbilling system, service processor or elsewhere in the network. Thisprovides the IPDR records for service usage policy verification andservice usage notification synchronization with little or no need tomodify existing billing or network apparatus.

In some embodiments, duplicate the IPDRs are sent from the networkequipment to the billing system and/or network management system thatare currently used for generating service billing or are used for devicemanagement or network management. In some embodiments, duplicate recordsare filtered to send only those records for devices controlled by theservice controller and/or service processor. For example, this approachcan provide for the same level of reporting, lower level of reporting,and/or higher level of reporting as compared to the reporting requiredby the central billing system.

In some embodiments, a bill-by-account billing offset is provided usingthe interface server. For example, bill-by-account billing offsetinformation is informed to the billing system through an existing datafeed and by updating the billing database using the interface server. Insome embodiments, transaction billing is provided using the interfaceserver. For example, transaction billing log information is provided tothe billing system through an existing data feed and by updating thebilling database using the interface server.

In some embodiments, existing/new service plan choice screens aredisplayed to the user, a user choice or decision/input is confirmed fora selected service plan, and then the service is implemented uponconfirmation of the billing system update for the new service plan. Insome embodiments, the service is implemented upon the user selection ofa new service plan and then retracted if not confirmed as updated by thebilling system within a certain period of time. In some embodiments, thenew service plan information is updated in the billing system through anexisting data feed or by updating the database using the interfaceserver.

Integrated Service Control

FIG. 51 illustrates a network architecture for locating servicecontroller device control functions with AAA and network service usagefunctions in accordance with some embodiments. As shown, an integrateddevice service control, AAA, device usage monitoring system 5110 isprovided that integrates service controller functions (e.g., servicecontroller device control system functions 4825 of FIG. 48) with accessnetwork AAA server 121 functions and network (e.g., real-time) serviceusage 118 functions.

FIG. 52 illustrates a network architecture for locating servicecontroller device control functions in the access transport network inaccordance with some embodiments. As shown, the service controllerdevice control system 4825 is located in the access transport network415, or in some embodiments, in the 4G/3G/2G RAN gateways 410 (asindicated by the dashed line with the arrow), or alternatively, in the4G/3G/2G transport gateways 420 (as indicated by the dashed line withthe arrow).

FIG. 53 illustrates a network architecture for locating servicecontroller device control functions in the radio access network inaccordance with some embodiments. As shown, the service controllerdevice control system 4825 is located in the radio access network 405,or in some embodiments, in the 4G/3G base station(s) 125 (as indicatedby the dashed line with the arrow), or alternatively, in the 3G/2G basestations 125 (as indicated by the dashed line with the arrow).

Ambient Services

In some embodiments, improved and simplified processes for provisioninga device or user for service on a central provider network, an MVNOnetwork or a virtual service provider (VSP) on the central providernetwork are provided. In some embodiments, provisioning includes one ormore of the following: a process or result of assigning, programming,storing or embedding into the device and/or network a set ofcredentials, or otherwise providing the credentials to the user; thecredentials being at least in part carried on the device or with theuser; and/or at least a portion of or a counterpart to the credentialsbeing stored or recognized by the network so that the various networkelements responsible for admitting the device access to the appropriateservice activities do so once the device or user service is active. Asan example, the credentials can include one or more of the following:phone number, device identification number, device security signature orother security credentials, device identification and/or securityhardware such as a SIM, device type identifier, one or more IPaddresses, one or more connection MAC addresses, any other addressidentifier, device service owner or VSP identifier, device OEM, devicedistributor or master agent, and/or any other information the networkcan use for admission control, authorization control, identifying thedevice with a service profile, identifying the device with an initialactivation or ambient experience, identifying the device with a serviceplan or authorized set of service activity capabilities, identifying thedevice with a service provider or service owner, identifying the devicewith an OEM or master agent, identifying the device with a distributoror master agent, or identifying the device with a user group or user. Insome embodiments, provisioning includes assigning, programming orembedding into the device and/or network the information to define thelevel of service activity, referred to as a service profile, that thedevice is authorized to receive. In some embodiments, provisioning alsoincludes establishing the device settings and/or network settings todefine an ambient activation experience in which the device userreceives a set of services after (e.g., within a short period of timeafter) purchasing or otherwise obtaining or installing the devicewhether the device has or has not been registered and activated with thedevice user or device owner.

In some embodiments, the ambient experience is the user experience thatis available at the time the device is sold in the event the user hasnot yet signed up for a service plan. For example, the ambientexperience is defined by an ambient service profile, an ambient serviceplan and/or the other service usage activity control policies in effectin the network, on the device, or a combination of both. For example, ifthe device service processor is used in large part to define the ambientservice profile, then the initial provisioning and activation settingsin the service processor, and possibly the service controller, candefine the user service upgrade offering choices, network destinationaccess control possibilities, traffic control policies, mobile commercetransaction capabilities (e.g., which transaction websites, WAP sites orportals the user can access to purchase information, content, music,games and/or eBooks), possibly free news or weather or other modestbandwidth Internet services that are provided free of charge to enticethe user into using/upgrading the service or using the transactions orviewing advertisements, what advertisements are displayed to the user orwhat advertisement based websites the user is exposed to, certainapplications may have access while others are blocked (e.g., Internetbased text services have access but email downloads do not), or otherexample service capabilities. It will be apparent to one of ordinaryskill in the art that allowing all of these services, and blocking otherambient user service attempts (e.g., unpaid large file size Internetdownloads or uploads or movie viewing or other access that would consumebandwidth and cause the ambient service to be a potential source oflosses for the service provider) is made possible by the service profilecontrol capabilities of the service processor and/or the servicecontroller. The bill by account embodiments, as discussed herein, inwhich each service activity can, for example, be separately tracked withthe service monitor and other agents and server functions to produce abilling offset that allows categorization and mediation of differentbilling entities (accounts) provides the capability for the serviceprovider to individually account for the costs of each ambient serviceelement. This allows business models wherein the free access to the enduser is paid for or partially paid for by one or more service providerpartners who are billed for service access using the bill by accountcapabilities (e.g., the transaction partners pay for user access totheir transaction experience and perhaps pay a revenue share fortransaction billing, the advertising sponsored website partners pay fortheir access service share).

While the service control capabilities of the service processor and thebill by account service cost sharing and transaction revenue sharing insome cases can create a profitable ambient business model, in othercases, the ambient services can be a potential source of losses for theservice provider. Accordingly, in some embodiments, the ambient servicecapabilities can be modified over time to reduce service cost to theservice provider or VSP based on a variety of decision factors. Forexample, the user can have one level of traffic control for a period oftime, and if the user has not signed up for service by the end of theperiod, the ambient service access is reduced by changing the servicecontrol policy settings in the service processor, and the service levelcan be further reduced over time if the user continues to not sign upfor service or the user does not create much transaction revenue. Asanother example, the recursive throttling algorithms discussed hereincan be utilized to one or more of the service activities offered inambient service mode so that the user experiences what full speedservice is like, and if the user continues consuming appreciablebandwidth with the service activity, then the activity is throttled backto reduce costs. In these examples, the service processor or servicecontroller can issue the user a notification explaining that theirservice is currently free so their usage is being throttled, and if theydesire to receive better service, service plan upgrade offers can bedelivered to the UI. It will now be apparent to one of ordinary skill inthe art that the various ambient service parameters, including theprovisioning and activation processes used to create the ambient serviceactivation, can also be managed by the VSP apparatus and processesdescribed herein. For example, this allows the same service controllersand service processor solutions to be used to define a wide range ofambient experiences for various device groups or user groups that arecontrolled by different VSPs.

Similarly, rather than controlling the ambient service profile settingsusing the VSP functions to control the service controller, serviceprocessor, provisioning and activation settings, other embodiments callfor the ambient service profile settings to be controlled by the networkbased service activity control equipment as similarly discussed herein.Depending on the level of service control and service monitoringsophistication (e.g., highly advanced DPI or service aware techniques),some, much, most or all of the above described ambient servicesfunctionality can be implemented using network based service controlsand the VSP management and control embodiments described herein.

In some embodiments, a device is suspended based on inactivity, or thedevice is placed in a suspended service state or suspended accountstate, so that the network does not get bogged down with a significantnumber of devices and credentials that are inactive. For example, thiscan also result in a portion of the device credentials being assignedback to an available pool rather than reserved for that particulardevice (e.g., phone numbers if phone numbers are scarce). The deviceaccount and/or activation state can be re-activated when the devicecomes back online. For example, the suspend state can be a simplesuspension of services without changing the account status, in whichcase the re-activation process can be automatically completed as asubset or entire set of the activation sequence that occurs when thedevice is initially used as described herein. The suspend state can alsoinvolve changing the account status to inactive, in which case there-activation process can automatically reconfigure the account statusback to an active state when the device re-accesses the network. Forexample, the suspend state can involve de-assigning or possiblyre-claiming a portion of the device credentials. If a portion of thecredentials are de-assigned, then when the device re-accesses thenetwork credentials can be automatically re-assigned as described invarious embodiments described herein.

Network Based Service Monitoring Notification and Control

In some embodiments, as described herein, it is desirable to implementsome or all of the deep service usage monitoring, service control orcontrol assistance, or service notification or notification assistanceassociated with a service profile in network apparatus rather than inthe device, or to implement some of the deep service monitoring,control, control assistance, notification or notification assistance inthe device and others in the network. This is the case, for example, ina mixed network in which some devices have some, or at least one, or allof the service processor capabilities discussed herein, but otherdevices do not have as much or any of the service processorcapabilities. Another example is for networks or devices that do nothave any service processor capabilities or where it is desirable to doall of the service monitoring, control and notification in the networkrather than the device. As described below, FIGS. 54 through 63 depictvarious embodiments for combinations of device based service monitoring,control or control assistance, usage notification or usage notificationassistance and/or network based service monitoring, control or controlassistance, usage notification or usage notification assistance.

FIG. 54 illustrates a network architecture for locating servicecontroller device control functions with AAA and network service usageincluding deep packet inspection functions in accordance with someembodiments. As shown, an integrated device service control, deviceusage monitoring system 5410 is provided that integrates servicecontroller functions including a deep packet control (DPC) policyimplementation function 5402 with access network AAA server 121functions and network real-time service usage 118 functions. In thefollowing discussion, it is understood that the AAA server 121 functioncan be re-located to another point in the network or network equipmentpartitioning with no loss in generality. It is also understood that manyof the functional partitions described for the various embodimentswithin integrated device service control, device usage monitoring system5410 can be re-drawn with no loss in applicability, function orgenerality. Finally, it is understood that one or more of the functionalelements described within the integrated device service control, deviceusage monitoring system 5410 can be removed for simplified embodimentsand that not all the functionality described herein is necessary in someembodiments.

In some embodiments, the integrated device service control, device usagemonitoring system 5410 provides for network based service monitoring orcontrol that satisfies various network neutrality and/or privacyrequirements based on indication(s) received from the device or user(e.g., user input provided using the device UI using the serviceprocessor 115; user input provided through another website, WAP site orportal; or user input provided through the service contract where theuser agrees to the monitoring and/or service control levels) and networkbased service control using a DPI service monitor 5412 and/or the DPCpolicy implementation 5402.

In some embodiments, the integrated device service control, device usagemonitoring system 5410 provides for network based service monitoring orservice control that satisfies various privacy requirements usingindication(s) received from the device or user (e.g., user inputprovided using the device UI using the service processor 115; user inputprovided through another website, WAP site or portal; or user inputprovided through the service contract where the user agrees to themonitoring and/or service control levels) and network based DPI serviceusage monitoring or DPC policy implementation using the DPI servicemonitor 5412 or DPC policy implementation 5402 as described below. Insome embodiments, the DPI service monitor 5412 and/or DPC policyimplementation 5402 include a secure database for storing servicemonitoring and CRM information for each device/device user. In someembodiments, the DPI service monitor 5412 and/or DPC policyimplementation 5402 can be integrated with the integrated device servicecontrol, device usage monitoring system 5410 (as shown) or providedwithin a separate router, server, and/or software/hardware implementedfunction that is in secure communication with the integrated deviceservice control, device usage monitoring system 5410 and/or othernetwork elements based on the network architecture. In some embodiments,a secure data store, such as a secure database, is not integrated withthe DPI service monitor 5412 or DPC policy implementation 5402 but is insecure communication with the DPI service monitor 5412 or DPC policyimplementation 5402, the integrated device service control, device usagemonitoring system 5410 and/or other network elements depending on thearchitecture (e.g., a billing server or any other network element). Insome embodiments, the user selects limits and/or restrictions on who canaccess remotely stored service usage history and/or other CRM/privacyrelated data (e.g., CRM/privacy gatekeeper settings), and, for example,other network elements and/or network administrators access to such datacan be limited and/or restricted accordingly. For example, access tosuch stored service monitoring and CRM information can require certainsecurity credentials and/or using various other well known secure datastorage techniques, such as the various secure storage techniquesdescribed herein.

In some embodiments, the secure database possessing user service usageinformation that is considered sensitive and has not been approved fordistribution by the user can be made unavailable to the credentialspossessed by network managers or network functions except, for example,for emergency service situations of government mandated monitoring needswhere special credentials are brought out of secure storage that are notnormally available. In some embodiments, rather than the user selectinglimits, a certain set of restrictions are assumed unless the userselects information filtering settings that allow more information to beshared with the network functions, network administrators or serviceprovider partners. In some embodiments, the information is filtered toremove information thought to be sensitive but still transmits serviceusage information needed for monitoring network services or otherimportant parameters. For example, the website destinations a user isvisiting can be classified with generic identifiers that are notdecodable or the individual website information can be completelyremoved. Many other examples will be apparent to one of ordinary skillin the art.

For example, the stored service monitoring and CRM information can alsobe organized into groups to define group CRM profiles to store servicemonitoring information for every user indexed by the user credentials(e.g., such groups can also be used for various VSP related functions,as described herein). The DPI service monitor 5412 or DPC policyimplementation 5402 also uses the secure storage to store servicemonitoring information for each user indexed by the user credentials oranother aspect of the device identifier or address assignment (e.g., IPaddress or MAC address). In some embodiments, a CRM information manager(e.g., a supervisor program executing on the integrated device servicecontrol, device usage monitoring system 5410) communicates with theother network functions and provides filtered service usage and CRMinformation according to CRM filtering rules for each user or for groupsof users. In some embodiments, the filtered CRM data can be madeavailable using secure communications with other networking equipment bythe integrated device service control, usage monitoring system 5410. Insome embodiments, the filter settings for some users allow moreinformation to be shared from the secure service usage information thanothers due to the differences in user preference settings and/or serviceplan agreements.

In some embodiments, user privacy preference information is used todetermine the privacy filter settings, which are securely implemented bythe integrated device service control, device usage monitoring system5410. For example, service CRM filter settings can be received at thetime of service contract sign up (e.g., service plan selection) and/orallow the user to log into service preferences web page to changesettings (e.g., without involving any interaction with local software onthe device). As another example, software on the device (e.g., includingthe service processor 115) can be used for selecting user CRM/privacypreferences, which are securely communicated to the integrated deviceservice control, device usage monitoring system 5410 (e.g., the devicecan include credentials that can be verified to allow forselection/modification of CRM/privacy preferences or other user basedpreferences securely maintained in a network server, such as theintegrated device service control, device usage monitoring system 5410or another network element, such as shown in various other embodimentsdescribed herein). In these examples, the filtered CRM data is availablefrom the integrated device service control, device usage monitoringsystem 5410 for other network components over a secure or opencommunication link. In another example, user CRM/privacy preferences areinput using a web server hosted by the integrated device servicecontrol, device usage monitoring system 5410 or the central billingsystem 123. In another example, software on the device (e.g., includingthe service processor 115) can be used for securely communicating userpreference decisions to an intermediate server that acts as a devicemanager and intermediate server for devices or device groups and theintegrated device service control, device usage monitoring system 5410.

In some embodiments, the integrated device service control, device usagemonitoring system 5410 provides for network based service control asdescribed below. In some embodiments and similar to the above describednetwork based CRM filtering embodiments, the DPI service monitor 5412 orDPC policy implementation 5402 includes secure storage (e.g., a securedatabase) for storing service monitoring information (e.g., based onuser selections/preferences), and the DPC policy implementation 5402performs traffic shaping/throttling algorithms for each user based onthe stored service monitoring information from DPI service monitor 5412.For example, network based DPI traffic inspection by the DPI servicemonitor 5412 can use the secure storage to save service monitoringinformation for each user indexed by the user credentials or otherparameters, such as IP address or other network tag. As another example,the DPC policy implementation 5402, for example, which can be supervisedby policy management server 1652 as described herein with respect tovarious other embodiments, can implement service usage historystatistical analysis inside the secure storage and maintain a serviceusage history analysis for each device/user and/or perform varioustraffic shaping and/or throttling algorithms based on various device,user selected and/or service plan related settings (e.g., for networkneutrality purposes) allowing for various higher level service usagegoals for one or more users, as similarly described herein with respectto various device based service usage monitoring embodiments (e.g.,except for certain encrypted network traffic flows or applicationrelated flows for which traffic control generally needs information fromthe application level and/or content specific traffic control).

In some embodiments, input is collected on how to implement servicecontrol (e.g., from the user of the device). For example, such input canbe determined based on one or more of the following: a service planchoice for the device; input provided by a user via a website (e.g., webbased portal) for indicating changes to service control policies, assimilarly described above; input provided by a user via the device(e.g., including the service processor 115), which securely communicatesthe input to the DPC policy implementation 5402, for example, which canbe supervised by the policy management server 1652; and input providedby a user via the device (e.g., including the service processor 115),which securely communicates the input to an intermediate server for theDPC policy implementation 5402, as similarly described above. In someembodiments, such service control is based on various algorithms asdescribed herein that identify the heaviest usage service activities andrecursively control the speed for those activities while leaving certainothers unaffected, and in a manner that is specified or selected by theuser to ensure network neutrality. In some embodiments, the user isoffered a choice for controlling service usage and/or selects analgorithm that controls all activities equally/neutrally (e.g., based onselected user preferences). For example, by implementing service controlalgorithms that are network neutral (e.g., throttling all activitiesequally or throttling the highest usage algorithms without singling outcertain activities for throttling unless they satisfy certain networkneutral usage history or usage statistics criteria), or that areapproved, selected or otherwise specified by the user, network neutraltraffic control or service usage control can be maintained.

In some embodiments, the DPI service monitor 5412, possibly inconjunction with the service usage notification 5420 and/or servicehistory server 1650, provides service usage/service cost (e.g., areal-time service usage counter) related notifications to the devicebased on user preferences, as similarly described above with respect tovarious device based service usage/service related notificationembodiments. For example, the DPI service monitor 5412, for example, inconjunction with the service usage notification 5420 and/or servicehistory server 1650, can perform service usage/service relatednotification algorithms based on one or more of the following: serviceplans, device settings, and/or user selected preferences (e.g., suchnotification messages can be securely communicated to the device and/orto the device via an intermediate server). For example, the policiesthat govern how the user is notified of service usage or service costcan be determined by the policy management server 1652 and/or theservice usage notification 5420. As another example, useracknowledgements of important notification messages and/or user choicesrelated to important service usage decisions can be requested, assimilarly discussed above with respect to device based serviceusage/control embodiments, which can then be communicated to the centralbilling system 123 as confirmation for any such important notificationmessages (e.g., related to service usage overage charges and/orconfirmation of service upgrades). In some embodiments, various otherservice usage algorithms related to service usage and/or service costforward projections described herein with respect device based serviceusage forward projection embodiments are performed in the network, suchas by the integrated device service control, device usage monitoringsystem 5410, and such forward projections can then be communicated toeach respective device as service usage notification messages (e.g.,using a push based approach (initiated in the network) and/or pull basedapproach (initiated by a request from the device)). For example, theseembodiments for projected service usage methods, as described herein,can be helpful for determining when the user is using services in amanner that will cause the user to run over a service limit so that theuser can be notified, or the service can be controlled or throttled ifthe user has selected a control or throttling option.

In some embodiments, one or more intermediate servers are provided forworkload balancing and/or off-loading the integrated device servicecontrol, device usage monitoring system 5410 and perform one or more ofthe functions described above with respect to various embodiments of theintegrated device service control, device usage monitoring system 5410.In some embodiments, service plans, device settings, and/or userselected preferences are used to associate each device/user with apreprogrammed profile to more efficiently associate such devices/userswith their selected service plans, device settings, and/or userpreferences. For example, the process of setting a service profile for agiven device can be determined by assigning the device to a service flowthat has the pre-defined service profile and is shared with otherdevices within the integrated device service control, device usagemonitoring system 5410 rather than individually processing the serviceflow manipulations for each device. In some embodiments, the act ofprovisioning and activating a service profile for a given devicesinvolves setting up the service flow definition and identifier withinthe integrated device service control, device usage monitoring system5410 (if it is not already set up) and then assigning the routing of thedevice credentials to that service flow identifier. User preferencescan, for example, be accounted for by assigning the device service flowto one of several pre-defined profiles based on user preferences thatare all supported under the same service plan. For example, one serviceflow profile can call for service usage notification but no controlunder the same service plan as another service flow profile that callsfor less notification but active service usage control to maintain usercosts to a monthly post-pay limit.

In some embodiments, the bill by account function is implemented in thecontext of the integrated device service control, device usagemonitoring system 5410 or other network based system embodimentsdescribed herein. For example, the DPI service monitor 5412, in somecases in conjunction with service history server 1650, can operate inconjunction with bill by account policy settings stored in the billingevent server 1662 so that service activities are divided into theaccount classifications defined by the service profile settings. Thebill by account feeds can then be sent to the billing system or to anintermediate billing event aggregation server that collects this type ofdeep packet inspection generated information from one or more integrateddevice service control, device usage monitoring system 5410 units toaggregate and format the information in a manner that may be used by thecentral billing system 123. In some embodiments, the bill by accountinformation collected in a network box like the integrated deviceservice control, device usage monitoring system 5410 is augmented bybill by account information collected on the device as described herein,and any intermediate server that can be used to aggregate and formatthese bill by account feeds for the central billing system deals withboth types of data, from the network and from the devices.

As shown in FIG. 54, in some embodiments, integrated device servicecontrol, device usage monitoring system 5410 includes the servicecontrol server link 1638, which, for example, can be used as describedabove (e.g., with respect to FIG. 16 and other embodiments describedherein) to communicate with device service processors 115. In someembodiments, billing server 1662 within integrated device servicecontrol, device usage monitoring system 5410 detects service usageevents reported by DPI service monitor 5412, in some cases inconjunction with service history server 1650, generates a billing eventthat can be recorded or transmitted to the central billing system 123.In some embodiments, billing server 1662 receives information fromdevice billing agent 1695 and/or device service monitor agent 1696 andtransmits the device service usage billing events to the central billingsystem 123. In some embodiments, certain billing events that areadvantageously collected in the network (e.g., DPI service monitor 5412and/or billing event server 1662) are combined with certain billingevents that are advantageously collected on the device (e.g., servicemonitor agent 1696 and/or billing agent 1695), and both sources ofbilling information are transmitted to the billing system 123.Similarly, in some embodiments, certain service usage information iscollected with service usage monitor agent 1696, and that information iscombined with service usage information collected from DPI servicemonitor 5412 and/or service history server 1650 and/or service usage118. In some embodiments, certain service aspects are controlled usingnetwork based DPC policy implementation 5402, in some cases inconjunction with or supervised by network based policy management server1652, and other service aspects are controlled using device based policyimplementation agent 1690, in some cases in conjunction with orsupervised by policy control agent 1692. As will now be apparent to oneof ordinary skill in the art in view of the numerous embodimentsdescribed herein, many hybrid approaches to service usage monitoring,service control, service notification or service billing can beaccomplished with some aspects of the policy, notification, control,monitoring or billing being implemented/performed on the deviceapparatus described herein and others implemented/performed on thenetwork apparatus described herein. The presence of access controlintegrity server 1662 and many other service control verificationembodiments described herein make it apparent that the integrated deviceservice control, device usage monitoring system 5410 embodiments alsoprovide for affirmative verification of whatever functions areimplemented on the device. It will also be apparent that all of theabove combinations of device and network functions, and many others, canbe accomplished in ways that are network neutral and/or protect userprivacy preferences by implementing the service control algorithms in anetwork neutral manner and/or receiving user preference input on how toimplement service control, and by maintaining service usage and CRMinformation security and filtering on both the device 100 and thenetwork based integrated device service control, device usage monitoringsystem 5410.

In some embodiments, the integrated device service control, device usagemonitoring system 5410 facilitates or plays a part in automatedprovisioning and activation of the devices as similarly described abovewith respect to various device based automated provisioning andactivation embodiments. In some embodiments, the activation server 160is integrated into or partially integrated into device service control,device usage monitoring system 5410.

In some embodiments, the integrated device service control, device usagemonitoring system 5410 facilitates ambient services as similarlydescribed above with respect to various device based ambient servicesembodiments.

In some embodiments, the integrated device service control, device usagemonitoring system 5410 facilitates VSP and ODI solutions as similarlydescribed above with respect to various device based VSP and ODIembodiments.

Various other network architectures for network based service controlincluding deep packet inspection functions can similarly be used as willbe apparent to one of ordinary skill in the art in view of the variousembodiments described herein.

FIG. 55 illustrates another network architecture for locating servicecontroller device control functions with AAA and network service usageincluding deep packet inspection functions in accordance with someembodiments. As shown, the service processor 115 is not present on thedevices 100, and the integrated device service control, device usagemonitoring system 5510 performs all service monitoring, service control,billing, and notification functions.

FIG. 56 illustrates a 4G/3G/2G DPI/DPC enabled gateway in accordancewith some embodiments. As shown, a 4G/3G/2G DPI/DPC enabled gateway 5610(e.g., implemented in either gateway 420 or gateway 410 or a combinationof both) where the conventional service gateway functions 5616 (e.g.,routing, switching, protocol translation/tunneling, charging datafunction (CDF), charging gateway function (GCF), mobility management,and/or suspend/resume) are combined with one or more of the followingembodiments and integrated into one or a combination of the servicegateways (e.g., RAN and/or transport gateways): DPI service monitor5412, service history server 1650, device usage 118, DPC policyimplementation 5402, policy management server 1652, user notification5618, billing event server 1662, access control integrity server 1654,service control service link 1638, data plane I/O 5612 (e.g., used torepresent the I/O port(s) for the gateway), and/or DPI/DPC gatewaycontrol plane link 5622 (e.g., used to represent the control planenetwork channel connecting the above elements to other network equipmentand in communication with gateway control communication 5620). Thepacket processing architecture shown in this figure calls for amulti-point to multi-point backplane bus scheme, but it will apparentthat other data path configurations are possible including serial. Aswill also be apparent, the above described configuration can also beapplied to either the transport gateway 420 and/or the RAN gateway 410.As mentioned above, it is possible to maintain a secure storage on the4G/3G/2G DPI/DPC gateway 420 or 410 that requires secure credentials toget into so that user privacy is protected and service usage informationor CRM information is filtered according to user preferences prior tosending to another network function or network manager, and the sameallowances can also be applied for emergency or government monitoringpurposes. Network neutrality can also be maintained in thisconfiguration by maintaining network neutrality in the service controlalgorithm and/or soliciting user input on how to control service usagejust as discussed above for other network service controlimplementations or as discussed in the device based service controldescriptions.

In some embodiments, the bill by account function is implemented in thecontext of the 4G/3G/2G DPI/DPC gateway 5610 embodiment or other networkbased system embodiments described herein. For example, the bill byaccount information can be completely derived from the network box(e.g., 4G/3G/2G DPI/DPC gateway 5610) without assistance from devicebased service monitoring or billing capabilities, or none may exist onthe device. In this example, the DPI service monitor 5412, in some casesin conjunction with service history server 1650, can operate inconjunction with bill by account policy settings stored in the billingevent server 1662 so that service activities are divided into theaccount classifications defined by the service profile settings. Thebill by account feeds can then be sent to the billing system or to anintermediate billing event aggregation server that collects this type ofdeep packet inspection generated information from one or 4G/3G/2GDPI/DPC gateway 5610 units to aggregate and format the information in amanner that can be used by the central billing system 123. In someembodiments, the bill by account information collected in a network box,such as the 4G/3G/2G DPI/DPC gateway 5610, is augmented, refined orotherwise added to by bill by account information collected on thedevice as described herein and any intermediate server that can be usedto aggregate and format these bill by account feeds for the centralbilling system deals with both types of data, from the network and fromthe devices.

FIG. 57 illustrates a network architecture including the VSP workstationserver 4910 in communication with the 4G/3G/2G DPI/DPC gateways 410 and420 in accordance with some embodiments. As shown, the VSP workstationserver 4910 is in communication with the 4G/3G/2G DPI/DPC gateways 410and/or 420, the Service Controller Design, Policy Analysis, Test,Publishing System 4835, and/or other networking elements includingpossibly the central billing system 123, the mobile wireless center 132(HLR) and/or the AAA server 121 for the purpose of provisioning and/orcontrolling settings in the 4G/3G/2G DPI/DPC gateways 410 and/or 420,the mobile wireless center 132 and possibly other equipment for thepurpose of implementing a portion of the VSP open partner functionalitydiscussed herein. In FIG. 57, the 4G/3G/2G DPI/DPC gateway 5610functionality as shown in FIG. 56 is implemented in the 4G/3G/2G DPI/DPCRAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 assimilarly described above. For example, the VSP functionality can alsobe used to set higher level policies associated with the 4G/3G/2GDPI/DPC gateway 420 or 410, such as provisioning or activation profilesor policies, ambient service profiles or policies, and/or bill byaccount service profiles or the other higher level service profile orservice plan embodiments discussed herein. In some embodiments, theprovisioning and/or activation steps described herein involve settingservice policies in the 4G/3G/2G DPI/DPC gateway 420 or 410. In someembodiments, ambient services or ambient activation involve setting upservice profiles within the 4G/3G/2G DPI/DPC gateway 420 or 410 thatallow the desired activities and block the undesired activities. Forexample, these settings can be included as part of the open serviceprovider partner programming capabilities of the VSP workstation server4910 embodiments.

FIG. 58 illustrates another 4G/3G/2G DPI/DPC enabled gateway inaccordance with some embodiments. As shown, a 4G/3G/2G DPI/DPC gateway5810 (e.g., implemented in either gateway 420 and/or gateway 410) isprovided in which the service processor connection (e.g., via servicecontrol server link 1638 as shown in FIG. 56) is not present so that allservice monitoring, control, billing event collection and transmission,and notification are performed by the 4G/3G/2G DPI/DPC gateway 5610(e.g., gateways 410 and/or 420).

FIG. 59 illustrates another network architecture including the VSPworkstation server 4910 in communication with the 4G/3G/2G DPI/DPCgateways 410 and 420, the AAA 121 and the mobile wireless center 132 inaccordance with some embodiments. As shown, FIG. 59 provides a networkdiagram corresponding to FIG. 58, with similar functionality to theembodiment shown in FIG. 57, in which the service processors 115 are notpresent on the devices 100. In FIG. 59, the 4G/3G/2G DPI/DPC gateway5810 functionality as shown in FIG. 58 is implemented in the 4G/3G/2GDPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway420 as similarly described above.

FIG. 60 illustrates a 4G/3G/2G DPI/DPC enabled gateway and servicecontroller device control system in accordance with some embodiments. Insome embodiments, enhanced network based service monitoring, control,billing and notification as discussed above is implemented using a4G/3G/2G DPI/DPC enabled gateway 6010 and service controller devicecontrol system 6025 as shown. In some embodiments, the functions shownin the figure to be inside of the service controller device controlsystem 6025 have been moved from the 4G/3G/2G DPI/DPC gateway 5610 ofFIG. 56 (e.g., or from gateways 410 and/or 420) so that they reside in aseparate server embodiment or other network equipment function separatefrom the 4G/3G/2G DPI/DPC gateway 6010. For example, this architecturecan be used when the network equipment manufacturer desires to separatethese functions or has an existing product that it is desirable toupgrade by adding a separate box. As another example, this architecturecan be used when the 4G/3G/2G DPI/DPC gateway 6010 is not capable ofkeeping up with large numbers of individual user profiles so it isdesirable to go to a scalable server configuration in which loadbalancing can be applied with a potentially more flexible programmingenvironment for implementing service policy management functions,statistical service history analysis algorithms, service usageprojection, and/or service control (or throttling) algorithms. In someembodiments, a secure storage is provided on the 4G/3G/2G DPI/DPCgateway 6010 and/or the service controller device control system 6025that requires secure credentials to get into so that, for example, userprivacy can be protected and service usage information or CRMinformation can be filtered according to user preferences prior tosending to another network function or network manager, and the sameallowances can also be applied, for example, for emergency or governmentmonitoring purposes. For example, network neutrality can also bemaintained in this configuration by maintaining network neutrality inthe service control algorithm construction and/or soliciting user inputon how to control service usage just as discussed above for othernetwork service control implementations or as discussed in the devicebased service control descriptions.

FIG. 61 illustrates another network architecture including the VSPworkstation server 4910 in communication with the 4G/3G/2G DPI/DPCgateways 410 and 420, AAA 121 and mobile wireless center 132 inaccordance with some embodiments. In FIG. 61, the 4G/3G/2G DPI/DPCgateway 6010 functionality as shown in FIG. 60 is implemented in the4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transportgateway 420, as similarly described above, and which are incommunication with the service controller device control system 6025 asshown.

FIG. 62 illustrates another 4G/3G/2G DPI/DPC enabled gateway and servicecontroller device control system in accordance with some embodiments. Asshown, the capability to communicate with the service processor 115 hasbeen removed so that all service monitoring, control, billing eventcollection and transmission, and notification are performed by the4G/3G/2G DPI/DPC gateways 6210 (e.g., implemented in gateways 410 and/or420) in conjunction with the service controller device control system6225 without assistance from the service processors 115.

FIG. 63 illustrates another network architecture including the VSPworkstation server 4910 in communication with the 4G/3G/2G DPI/DPCgateways 410 and 420, AAA 121 and mobile wireless center 132 inaccordance with some embodiments. In FIG. 61, the 4G/3G/2G DPI/DPCgateway 6210 functionality as shown in FIG. 62 is implemented in the4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transportgateway 420, as similarly described above, and which are incommunication with the service controller device control system 6225 asshown.

As will be apparent to one of ordinary skill in the art, the abovedescribed embodiments can be extended to include some or all of thefunctions depicted in the 4G/3G/2G DPI/DPC service gateways of FIG. 56in the base station or base station controller 125.

Provisioning and Activation

In some embodiments, automated provisioning and activation includesautomation of one or more of the following functions: (1) programmingdevice credentials or partial credentials and recording them in adatabase (or providing same when they are programmed into the device),(2) associating these credentials with the proper provisioning and/oractivation actions to be taken on the device and in the network, (3)directing the device to the proper activation function (e.g., activationserver) sequence when it attempts to connect to the network, (4)completing provisioning of the device, (5) programming the AAA, billingsystem, gateways, mobile wireless center and other network equipment tothe proper initial device service control settings, and (6) establishinga service account for the device.

In some embodiments, improved processes for activating service for adevice or user with a network service provided by a central providernetwork, an MVNO network or a VSP on the central provider network areprovided. In some embodiments, activation includes one or more of thefollowing: a process or result of associating a service account withdevice or user credentials; with the service account potentially furtherbeing associated with a service profile defining the service activitiesthat the device is authorized to access; creating or updating a serviceusage or billing record and associating it with the service account tocreate a service plan; and/or initiating service to the device or userin which the network equipment allows access to the appropriate level ofservice activities. In some embodiments, VSP embodiments include theprovisioning and activation apparatus embodiments of any or all forms.

In conventional mobile device provisioning systems, the provisioning andactivation process required to create a user service account and enablethe device to access the desired level of service activities can limitmass market, low cost or user friendly applications of the device orservice, because the process can often be cumbersome, time consumingand/or expensive for the service provider, service owner, master agent(service distributor), MVNO, VSP and/or user. Accordingly, the variousembodiments for provisioning and activation described herein simplifythe provisioning and activation process for mobile devices. In someembodiments, provisioning and activation for the device and/or thenetwork accommodates a wide variety of device types and service profiletypes, with the capability to perform the provisioning and activation ata number of points in the manufacturing, distribution, sales and usageprogression for the device, and the ability to either pre-activatebefore first device use or very quickly activate during first device use(or during some later use of the device).

In some embodiments, as described herein, the term provisioninggenerally refers to those actions/processes associated with programmingthe device with credentials or other device settings or softwareinstallations used to later activate the device, as well as, in someembodiments, creating database entries and other credential associationsin the network so that the network and/or device have the informationused to recognize the device or credentials and implement the servicepolicies in the service profile and/or service plan once the serviceprofile and/or service plan are activated. In some embodiments, asdescribed herein, the term activation generally refers to the process ofcreating or selecting the service plan and/or service profile,programming the settings that are used in each (e.g., required) networkfunction and/or each (e.g., required) device function so that the systemcan properly associate the device credentials with the appropriateservice activity policies, and then admitting the device onto thenetwork. The term activation can also refer in some embodiments to thecreation of a user or device service account, in some cases, with useror device owner information or billing information. In some embodiments,the process of provisioning amounts to assigning credentials to thedevice and programming a portion or all of the credentials on thedevice, entering a portion or all of the credentials in the variousnecessary network equipment databases so that the network components arecapable of identifying the device and associating it with the networkbased portion of the admission, traffic processing, service monitoring,billing, service limits and other policies that are eventually definedby the service profile and service plan.

Further examples of the network based service profile policies includenetwork access level, traffic routing, service monitoring, servicelimits and actions taken upon reaching service limits. Once the serviceprofile is created and activated during the activation process, thedevice credentials and the associated service profile are communicatedthroughout the necessary network elements so that each element canimplement its part of the network portion of the service profilepolicies. This process of propagating the service profile settings toall the required network equipment components is a portion of what isreferred to herein as activation in accordance with some embodiments. Insome embodiments, the activation process includes associating thecredentials with the proper service plan and/or service profile, andpossibly completing the process of programming the device functionsand/or network functions so that the device can be admitted to theappropriate level of network services. In some embodiments, activationalso includes the service processor software settings, configurations orinstalls for each function or agent in the service processor toimplement its part of the service profile, service plan, service billingor transaction billing policies. In some embodiments, activation alsoincludes the creation of entries in the various service accountdatabases and/or billing databases to create a user account or deviceowner account for the purpose of managing the user choices for serviceplan and other account information storage and management aspects, suchas maintaining status information, maintaining the central serviceprofile configuration, conducting reconciliation and billing exchanges,service usage history, and/or account history.

In some embodiments, the term credentials generally refers to the set ofinformation parameters that the network and/or device uses (e.g.,requires) to admit the device onto the network and associate it with theappropriate service profile and/or service plan. For example, thecredentials can include one or more of the following: phone number,device ID, hardware security device ID, security signatures, IP or MACaddress, signature algorithms, passwords, or other secure authorizationprocesses, service provider, OEM, master agent (service distributor),device distributor, VSP, service processor settings or version, or otherinformation used/required by the network to authorize network admissionor activate service. In some embodiments, at least some of thecredentials are unique to the device, and, in some embodiments, groupsof devices share one or more aspects of the credentials. In someembodiments, the term permanent credentials generally refers to the setof credentials that include at least a subset that are intended to beassigned to a device or user on a permanent basis. In some embodiments,the term temporary credentials generally refers to the set ofcredentials that include at least a subset that are intended to beassigned to a device or user on a temporary basis. In some embodiments,temporary credentials are eventually replaced by permanent credentials.In some embodiments, at least some elements in the temporary credentials(e.g., phone number and/or access or authorization security credential)are used for more than one device. In some embodiments, the temporarycredentials are recycled from one or more devices and used for one ormore other devices, for example, when they remain unused for a period oftime or when they are replaced with permanent credentials on one or moredevices. It should not be inferred from the term permanent credentialsthat permanent credentials are never recycled, for example, when theuser discontinues service or use of the credentials. Also, the termtemporary credentials does not imply that temporary credentials arealways temporary. In some embodiments, partial credentials orpre-activation credentials generally refer to a subset of credentialsthat are to gain access to limited network services for the purpose ofprovisioning of credentials and/or activation of a service plan orservice profile. For example, prior to a phone number being assigned, adevice can gain access to a limited set of network server destinationsin which embedded information contained in the device (e.g., the partialcredentials) is provided to the server, the server associates thatinformation with the proper additional credentials (including the phonenumber) to assign to the device and/or associates the information withthe proper service profile to activate service. In this example, partialcredentials can include device type, OEM, service provider, VSP, deviceidentification number, SIM, service processor configuration or someother information used by the server to determine what the credentialsshould be and the proper service profile.

In some embodiments, a permanent service account generally refers to theservice account that is permanently associated with the user and/ordevice. For example, this account includes an association with thedevice or user credentials, user information or billing information,service profile, billing profile, network authorization status and otheraspects that define the device or user service policies and billingpolicies. In some embodiments, the term temporary service accountgenerally refers to a service account that is temporarily set up andassociated with the device before some or all of the required permanentaccount information is available or entered for a device or user. Forexample, this account can be set up with an association with an actualuser, or can be set up with a mock user or unassigned user associationso that the network and billing system can recognize the credentials,authenticate the device, admit the device, provide the proper level ofservice activity control according to the service profile associatedwith the temporary service account, or collect the service activityusage information for various network and billing system accountingneeds before actual user information or billing information has beenentered into the network systems. For example, a temporary serviceaccount can make it possible or easier to use existing billing systemsor other network systems to provide simplified provisioning, simplifiedactivation or ambient services. A temporary service account can alsobecome a permanent service account by replacing mock user or unassigneduser information with actual user information, or a temporary serviceaccount may need to be replaced by a permanent service account whenactual user information needs to be entered into the network systems,possibly including the billing or service profile databases.

In some embodiments, temporary or permanent device credentials and otherinformation used/required for provisioning the device are generated withapparatus located at the manufacturer or in the distribution channel asdiscussed below. In some embodiments, the apparatus includes a localonsite server that typically shares some aspects of the provisioninginformation (e.g., phone number, phone number range, MEID or MEID range,SIM number or SIM number range, IP address or IP address range, MACaddress or MAC address range, other secure device credential elements)with a network provisioning database. In some embodiments, the apparatusincludes a server terminal, and the aforementioned portion of thecredentials is generated by the network and shared with the localprovisioning apparatus. In some embodiments, as will be discussed below,the provisioning credentials are in part generated in the network andshared with the device while it is connected online to an activationserver (e.g., activation server 160) that is connected to the accessnetwork. Similarly, there can be activation servers connected toapparatus in the manufacturing or distribution channel that servicedevice activation, or over the air or over the network apparatusconnected to an activation server, which in turn connects to the device,can be used to accomplish activation programming of the network anddevice as further discussed below.

In some embodiments, when a device is provisioned and entered into thenetwork provisioning database, it is associated with the automaticprovisioning and/or activation sequence the device is intended to gothrough once it connects to the network or to the apparatus that willcomplete the process. In some embodiments, one or more device parameters(e.g., service owner, device type, OEM, plan type, IP address, securitycredential and/or software version) are used to determine what theappropriate network provisioning steps and/or settings are forcompleting the provisioning and/or activation process, and thisassociation information is stored in the network provisioning databasefor propagation of the provisioning profiles or activation profiles tothe various network equipment elements. In some embodiments, the networkprovisioning database is provided (e.g., in the network) that associatesthe pre-activation provisioning information (e.g., generated, asdescribed herein, at time of manufacture, sometime during distribution,by the user on a website by a sales associate or other activationassistant, or by the network when a new device enters the automaticactivation process). For example, the pre-activation provisioninginformation informs the network whether or not to let the device onto anactivation sequence when the device attempts access, and in some cases,also instructs the network to direct the device to a specific activationsequence including, for example, an activation server (or otheractivation sequencing apparatus) sequence as described herein. In someembodiments, a central database is queried by other network equipment orthe central database is included in one or more of the network elements(e.g., the AAA server and/or billing system, mobile wireless center132), or the database is copied in part or in whole in various networkelements (e.g., the central database, AAA server, mobile wirelesscenter, billing system and/or gateways).

In some embodiments, propagating the network equipment provisioninginformation for a given device or group of devices is accomplished witha network provisioning system that has access to the networkprovisioning database and is capable of programming the appropriatenetwork equipment. In some embodiments, this network equipment isreferred to as “network management” equipment or “network provisioning”equipment. In some embodiments, there are several functions that takepart individually or in concert, including, for example, the AAA server121, service controller 122 (either with device based/assisted servicesthrough the service processor related embodiments or with network onlyembodiments as described herein), the mobile wireless center 132 (e.g.,including the home location register (HLR) or other similar functionreferred to by other industry terms), the activation server(s) 160,other network provisioning or management equipment attached to orassociated with the billing database system, and/or some other equipmentapparatus. In some embodiments, the local database on the device,database in the AAA server and/or database elsewhere in network isprovisioned to inform the gateway of the process for handling thepre-provisioned device according to, for example, the credentials. Forexample, if the device is not recognized or not authenticated onto theaccess network as an activated device with associated active serviceprofile and/or service plan, the device connection or communication canbe directed (or routed) to a generic activation server that provides anactivation sequence that is not necessarily determined by one or more ofthe specific device credential elements, partial credential elements,device profile or partial device profile that define something specificabout the activation sequence for the device. In another example, inwhich the device is not recognized or authenticated as an activateddevice with associated service profile and/or service plan, the devicecan be directed (or routed) to an activation service (or otheractivation sequencing apparatus) that uses some part of the credentialsor range of partial credentials or a portion of a partial or completedevice profile to determine a desired pre-determined device specific ordevice group specific activation sequence that is implemented by aspecific activation service sequence or other activation sequenceapparatus. In another example, in which the device is not recognized orauthenticated as an activated device with associated active serviceprofile and/or service plan, a portion of the device credentials orpartial credentials can be used as a look-up index into a database thatdetermines what the specific device activation sequence should be, andthe device can be directed (or routed) to a specific activation serversequence or other activation sequencing apparatus.

In some embodiments, a database in the AAA server or database elsewherein network is provisioned to inform the gateway what to do with apre-provisioned device according to the credentials. For example,devices can be authenticated (for activated devices), routed toactivation servers (or other activation sequencing apparatus) or deniedaccess. In some embodiments, the AAA server (and/or other networkelements) provide the above discussed look-up function for the abovegateway description in which a lookup database, locally stored or storedin a central database, is queried to provide secondary routinginformation to the specific or generic activation servers.

In some embodiments, the pre-provisioned database is located in thebilling system. In some embodiments, the billing system accesses thepre-provisioned database (e.g., stored on the billing system or anothernetwork element) for the purpose of setting up temporary accounts orpermanent accounts and associating those accounts with pre-activationstatus, activated free ambient or activated paying customer.

In some embodiments, for zero activation, all the requiredpre-provisioning or programming of the above network elements, orothers, is coordinated by the network provisioning system at some pointafter the partial or full device credentials have been associated withthe device or reserved for a particular device type or service type. Insome embodiments, the network provisioning system also coordinates theinformation to or from the device provisioning apparatus that isdescribed elsewhere.

In view of the various embodiments described herein, it will beappreciated that many of the automated or background provisioning,activation and ambient embodiments described herein can be accomplishedwith network based approaches, device based approaches, ornetwork/device combination/hybrid based approaches. For example, whenthe access control for the provisioning process is accomplished in thedevice (e.g., a device based approach), the activation server can belocated anywhere on the Internet, and the device will ensure that theactivation process is conducted with the activation server whileblocking other traffic from occurring. As another example, some or allof the ambient provisioning programming steps become steps to programthe access control, traffic control, application control, bill byaccount rules, and/or other aspects in the service processor or servicecontroller as described herein.

In some embodiments, the provisioning apparatus described herein can bea computer located in the user's home or business, and the user or an ITmanager has access to a website that provides the provisioninginformation, in which the computer serves as the provisioning orsoftware programming apparatus. In some embodiments, the network itself,possibly through an activation server 160, website or other interface tothe device, becomes the provisioning apparatus, in some cases, with theassistance of software on the device to affect the programming ofprovisioning information from the network or the communication of devicecredentials or other information to the network. For example, thissoftware can be a background process that runs without user interaction,a portal/widget program, a web browser based program, a WAP browserbased program, and/or any other program that provides a counterpartfunction to the network functions effecting the provisioning (e.g.,activation server). In some embodiments, the activation server eitherinitiates a specific provisioning sequence if device software is presentto assist or routes to a website for manual entry if there is nosoftware present.

FIG. 64 illustrates another network architecture including a systemlocated in the manufacturing or distribution chain for the device thatprovides the device provisioning or partial provisioning, and anypre-activation required for the device to later activate on the networkin accordance with some embodiments. Device credential, software andsettings server 6420 provides a link to the network functions thatgenerate or provide device credentials, and/or associate devicecredentials with activation profiles or pre-activation profiles in thenetwork equipment (e.g., the billing system 123, service controllerdevice control system 6225, gateways 410, 420, base station 125,credential generation and association server 6410, activation server160, service download control server 1660 and/or other networkapparatus). For example, the link between the device credential,software and settings server 6420 to the central provider core networkequipment can be over the Internet 120 (e.g., a secure link over theInternet) as shown or over another connection such as a leased line. Thedevice credential, software and settings server 6420 obtains credentialsor partial credentials from the network apparatus that generates them,illustrated by the credential generation & association server 6410.Credential generation & association server 6410 need not be directlyconnected to the central provider core network 110 as shown, but can belocated elsewhere (e.g., in another location connected by a secureInternet link). Credential generation & association server 6410 assignscredentials, or partial credentials, for use by device credential,software and settings server 6420. When these credentials are assignedto a device, they are programmed, loaded or otherwise associated withthe device by device credential provisioning apparatus 6430, which isconnected to the device wirelessly or via a wire line connection.

In some embodiments, a device software loading and programming apparatus6440 provides software loading or device settings functions that form aportion or all of the provisioning or pre-provisioning deviceconfiguration, or form a portion or all of the device activation profileconfiguration, or form the device service owner, master agent or VSPdevice assignment or signature, and in some embodiments, using anactivation tracking service (ATS) system. As discussed herein, the ATSmonitors network connections and aspects of traffic that provide insightinto which networks the device 100 is gaining access to, in someembodiments, for the purpose of ensuring that an OEM, master agent,device service owner or VSP is being compensated for devices thatactivate on a service provider network. In some embodiments, the ATSagent connects to a server counterpart that records and, in someembodiments, also analyzes the service or network connection informationto make a determination of the type of access service the device isreceiving and, in some cases, determine which networks the device isactivated on. In some embodiments, the ATS is installed on the device ina manner that makes it difficult to tamper with or remove so that theentity that is intended to get credit for device service activation doesget credit (e.g., the ATS agent can be loaded into secure memory, it canbe installed with software that makes it difficult to de-install, it canbe installed on the modem possibly in secure memory, it can be installedin the BIOS, it can be installed deep in the OS kernel, it can beinstalled with one or more additional device agents that monitor the ATSagent and alert a network function or re-install it if tampered with).The SIM inventory 6450 is provided to illustrate that, in someembodiments, hardware elements (e.g., a SIM security module as shown) orhardware configurations are also installed or manipulated in device 100and these operations and the recording of the resulting associationsform a portion of the provisioning or pre-provisioning process.

In some embodiments, at the time the credentials or partial credentialsare loaded, programmed, set, installed, read from the device orotherwise recorded, they are, in some cases, all associated together ina database that allows for later identification of the device and itsappropriate provisioning and/or activation process through suchassociations. For example, this can involve reading device parameterssuch as MEID, MAC address, device type, or other information that isassociated with the information being loaded or configured on thedevice. As discussed herein, this credential configuration andassociation information is stored in the network equipment responsibleusing it to configure the network to activate the device in one of thevarious embodiments disclosed herein.

Some embodiments include tying some or all of the activationprovisioning steps and information settings together into a databasethat defines a higher level activation profile for a group ofusers(/devices), and a server is used to perform device and equipmentprogramming for the devices in the group, including, for example,associating the following device information into the group definition:credentials, service owner or master agent, provisioning informationand/or activation profile. Some embodiments further provide for thisdevice group information being distributed to the various networkequipment components required to activate the devices as discussedelsewhere. In some embodiments, this programming and device groupassociation is accomplished using the VSP workstation server 4910. Forexample, a device can be manufactured and distributed in a manner thatprovides flexible assignment of the device to a group that is assignedto an activation profile or a service owner.

In some embodiments, multiple activation servers 160 are provided (asshown), which illustrates that there can be multiple device activationservers 160 each with a different device activation experience andpotentially controlled by a different VSP, service owner, serviceprovider, OEM or master agent. As discussed herein, there are severalways that a device 100 can be routed to the proper activation server 160so that the device provisioning and activation process can be completed.In some embodiments, all devices that are not activated are re-directed(or routed) to an activation server that reads one or more parameters inthe device credentials. The device credential information can bedetermined either through the device identification informationassociated with the access network connection itself (e.g., MEID, IPaddress, phone number, security credentials, or other credentialsidentified for a device that gains access with the network), or with theaid of the device in a pre-arranged query-response sequence. The devicecan then be re-directed (or routed) to the appropriate activation serverfor that device, device group, device service owner or VSP. In someembodiments, the same process described above can be accomplished with asingle re-direction from a service gateway 420 or 410, or another routerenable network element. In some embodiments, the gateway or networkelement itself decodes the device credential information as describedherein and performs the correct re-direct (or route) to the appropriateactivation server 160 for that device. In some embodiments, theactivation server 160 can be incorporated directly into the gateway 420or 410, the base station 125 or other network component. In someembodiments, the activation server 160 can be incorporated into theservice controller 122 or the service controller device control system6225.

In some embodiments, apparatus other than the activation server are usedto facilitate provisioning of credentials or partial credentials, oractivation, during manufacturing or device distribution, and, forexample, these apparatus can augment, supplement, compliment or replacethe activation server function. Such apparatus include, for example,device programming equipment (e.g., device credential provisioningapparatus 6430, device software loading and programming apparatus 6440or SIM inventory 6450), equipment that is networked into a centralprovider, MVNO or VSP database (e.g., device credential, software andsettings server 6420) to gain access to provisioning information oractivation information that is programmed into a device or group ofdevices, or to place device credential or partial credential informationin a network database for later recognition, or to receive orcommunicate security information such as certificates for devices or SIMmodules that will later be used to complete provisioning or completeactivation or gain access to a network. For example, these apparatus, orany other apparatus including the activation server, can be networkedinto a service provider network or device database, an MVNO network ordevice database or a VSP network or device database. In someembodiments, programming of the device credentials or other informationassociated with the service processor or device is provided, so that,for example, the device can be recognized by an activation server orsimilar network function at a later point in time so that provisioningor activation can be completed in an automated manner, potentially withreduced or no user involvement, that provides a provisioning oractivation configuration that is in some way unique for the serviceprovider or service provider partner, device type, user group, VSP,MVNO, master agent or other entity. In some embodiments, thisprogramming is provided in a manner that is difficult to change withoutthe proper authorization so that the device is properly associated withthe proper “service owner” or master agent (e.g., for the purpose ofactivation incentive payments). For example, as discussed herein,various approaches can be applied to the device credential or othersettings or software provisioning so that the settings or software aresecure or protected, or so that if the software is removed, replaced ormodified it is reported or replace or restored. In some embodiments, VSPcontrol of the provisioning, partial provisioning or activation ofdevices is provided during manufacture or at different points in thedistribution channel. As discussed herein, some of these embodimentsallow the central provider to offer to service partners (e.g., VSPs,MVNOs, master agents, and/or OEMs) similar types of control for deviceactivation experience design or device service assignment control (e.g.,sometimes referred to as service provider device locking so that otherservice providers cannot provide primary access to the device) duringthe manufacturing or distribution process that are possible with devicesmanufactured and distributed for the central service provider.

In some embodiments, the device is provisioned before the user obtainsthe device with permanent credentials, temporary credentials or partialcredentials. In this case, the necessary credential programming of thedevice occurs during manufacture, at some point in the devicedistribution, such as at a distribution depot or in a store, or at thepoint of sale or point of shipment. In some embodiments, provisioning ofnetwork information as discussed above is used, and the networkinformation is provisioned at the same time, before or after the deviceinformation is provisioned. In some embodiments, the device provisioninginformation is programmed with dedicated apparatus that connects to thedevice either with wires or wirelessly. For example, the dedicatedapparatus can be local to the location where the device is beingprovisioned, or it can be partially or entirely networked into adatabase or provisioning solution located elsewhere and operated by thecentral provider, a VSP, OEM or other entity. For example, the apparatusto program the network portions of the provisioning information can alsobe networked and the operators who set up the required networkprogramming for a device or group of devices may be in the vicinity ofthe servers that host the provisioning and management tools or they maynetwork into the servers. In some embodiments, provisioning systemoperators have full or partial control of any device provisioningequipment associated with the entity they work for (e.g., OEM, VSP ormaster agent) but only have remote access via secure terminal, securewebsite or other techniques to network into a central provider or VSPserver farm in which they control or partially control the networkportion of provisioning capabilities for that subset of devices that areassigned to the entity they work for with (e.g. OEM, VSP or masteragent).

In some embodiments, provisioning is accomplished over the air on themobile access network for mobile devices, or over the wired accessnetwork or WLAN connection for wired access networks, either before theuser receives the device or after the user receives the device. In somecases, the device can be connected to general purpose equipment, such asa computer to perform the programming required to complete provisioning.In the cases in which the device is provisioned at point of sale orafter point of sale, the device provisioning can be triggered by a userinitiated sequence, or can be initiated by an automated backgroundsequence at any time after the device is powered on. In such cases, insome embodiments, partial credentials that include information such asdevice type, OEM or service provider are used to assist in determininghow to complete the provisioning, and the information can also includesecure information, certificate or signature programmed into the partialcredentials that is required for the network to perform the provisioningof the remaining credential information in the device and possibly thenetwork. In some embodiments, any network information used/required toprovision the device or service is generated at the time the partialcredentials are determined rather than beforehand.

In some embodiments, the device is activated for service before the userobtains the device with permanent credentials, temporary credentials orpartial credentials, or with a permanent service account or a temporaryservice account. For example, in this case, the necessary steps ofprovisioning and activating service for the device can occur duringmanufacture, at some point in the device distribution, such as at adistribution depot or in a store, or at the point of sale or point ofshipment. In some embodiments, the steps for activating service includeone or more of the following: provision the device (e.g., withpermanent, temporary or partial credentials), provision the necessarynetwork databases and equipment to prepare them to recognize the deviceand associate it with the service profile and/or service plan, create orselect the service account (e.g., permanent or temporary serviceaccount), select or create the service profile and/or service plan,program any elements in the device required to activate service (e.g.,account ID, device aspects of the service profile and/or service plan),and program the necessary network databases and equipment with therequired associations of device credentials and service profile and/orservice plan policy settings. In some embodiments, the device orientedprogramming portions of the service activation steps occur at the sametime, before or after the network oriented programming portions of theservice activation steps.

In some embodiments, the device activation information is programmedwith dedicated apparatus that connects to the device via a wireless orwire line connection. For example, the dedicated apparatus can be localto the location where the device is being provisioned, or the dedicatedapparatus can be partially or entirely networked into a database orservice activation solution located elsewhere and operated by thecentral provider, a VSP, OEM or other entity. For example, the apparatusto program the network portions of the activation information can alsobe networked and the operators who set up the required networkprogramming for a device or group of devices can be in the vicinity ofthe servers that host the service activation and management tools orthey can network into the servers. In some embodiments, activationserver tools operators have full or partial control of any deviceactivation apparatus associated with the entity they work for (e.g.,OEM, VSP or master agent) but only have remote and partial access viasecure terminal, secure website or other techniques to network into thenetwork portion of the activation tools that are controlled by thecentral provider or VSP. The server tools operators can be restricted insome embodiments to providing network activation information or settingsonly for those devices or device groups that are assigned to the entitythey work for with (e.g., OEM, VSP or master agent). For example, thedevice control group restriction can be accomplished with a securedatabase that has secure sub-partitions for one or more entities so thatthey cannot impact the control of one another's network activationsettings but can control their own devices. In this way, a centralizedset of activation tools resources controlled by a central provider, VSPor other entity can be partitioned so that different entities can havepartial or full control of the activation service definition for devicesor groups of devices without impact or risk to others who share thenetwork and activation tools resources.

In some embodiments, activation is accomplished with an over the airinterface to a mobile device, or over the wired access network or WLANconnection for wired access networks, either before the user receivesthe device or after the user receives the device. In some cases, thedevice can be connected to general purpose equipment such as a computerto perform the programming required to complete activation. In the casesin which the device is activated at point of sale or after point ofsale, the final device activation process can be triggered by a userinitiated sequence, or can be initiated by an automated backgroundsequence at any time after the device is powered on. In such cases, someembodiments call for a temporary service account that is used to bringthe device onto the network before the user has input the informationnecessary to create a permanent service account. In some embodiments, atemporary or permanent service account can be applied to the device atthe time the device reaches the network, and the type of account,service profile and/or service plan can be influenced (e.g., partiallydetermined or informed) or determined by information embedded in thedevice credentials or partial credentials, such as device type, deviceID, SIM, OEM or service provider. For example, the device credentialscan also include secure information, certificate or signature that canbe required by the network to perform the activation steps for temporaryor permanent service account status. In some embodiments, in which thedevice is activated in this manner before the user information isavailable, or before the user has selected a pay for service plan, theservice profile and service plan are set up for ambient services asdescribed herein.

In some embodiments, the device is activated during the manufacturing ordistribution process, and then the activated device status is suspended.Once the temporary or permanent service account is set up, withappropriate service profile and/or service plan and temporary orpermanent credentials, in some networks and billing systems the servicecan often be more easily resumed once suspended as compared toprovisioning and activating the device from scratch. The device is thenlater resumed (or re-activated) when some event triggers the resumeprocess, such as when it ships to the end user or when the end userattempts to use it. This process prevents the network from needing tomanage credentials and accounts for devices that have been activated butare not yet on the network.

In some embodiments, provisioning is accomplished at least in part withtemporary credentials in a manner which is automated and convenient forthe user or device owner. In some embodiments, at least some subset ofthe temporary credential elements replaced at a later point in time bypermanent credential elements in a manner that is also automated andconvenient for the user or device owner. In some embodiments, thetemporary credential set is pre-programmed into the device along with atemporary or permanent service account including service profile duringthe manufacturing or distribution process so that the device isactivated with temporary credentials when it ships. In some embodiments,the aforementioned pre-programming is performed for the network via asecure set of server access equipment that networks into the networkdatabases used to define the service profile and/or the service plan. Insome embodiments, a subset of the temporary credentials is recycled onceit is replaced, if a temporary service account is not activated or usedafter some period of time, if a permanent account is not activated orused after some period of time, or if the credentials subset is revokedfrom the device for some other reason.

In some embodiments, more than one device is assigned one or moreelements of the temporary credentials, such as the phone number, whichmay be limited in supply. In some embodiments, a network will acceptmore than one set of temporary credentials, one or more redundantelements, for two or more different devices. In some embodiments, adevice that has two or more temporary credential sets, in which at leasta subset of the credential elements are different for the sets, so thatif one set of credentials has elements that are already being used toaccess the network, then one or more reserve sets can be drawn upon togain access to the network.

In some embodiments, the temporary credentials are used to log onto thenetwork to conduct an over the air or over the network activationprocess in which an activation server reads at least a portion thedevice credentials to determine some aspect of how the device serviceprofile. In some embodiments, the aforementioned over the air activationprocess is accomplished in the background without user intervention. Insome embodiments, the over the air activation process is initiated whenthe user first attempts to use the device or when the user firstattempts to access the network or upon user request or approval. In someembodiments, the over the air activation process is initiated using atemporary service account for the device and/or network to gain accessto the network. In some embodiments, the over the air activation processis initiated after the user has entered the information required tocreate a permanent user account into the device or into the network. Insome embodiments, the user is required to enter the aforementioned userinformation before using the device or using some aspect of the device.In some embodiments, the temporary service account is replaced by apermanent service account some time after the user has entered thenecessary information to create a permanent account into the device ornetwork. In some embodiments, the over the air activation process isinitiated using a permanent service account assignment for the deviceand/or network to gain access to the network.

In some embodiments, the service profile is assigned to the deviceand/or network during the aforementioned over the air activation to be apay for service profile with a free trial period. In some embodiments,the service profile assigned to the device and/or network during theaforementioned over the air activation includes pre-pay, post-pay,session based pay or pay as you go options for service. As will beapparent to one of ordinary skill in the art, various embodimentsdisclosed herein are particularly well suited for control or pre-payservices. In some embodiments, the service profile that is assigned tothe device and/or network during the aforementioned over the airactivation is an ambient service profile providing service access beforeall the user information is available to assign a permanent account. Insome embodiments, the service profile that is assigned to the deviceand/or network during the aforementioned activation is an ambientservice profile providing a service upgrade selection option interfaceto the user. In some embodiments, the service profile that is assignedto the device and/or network during the aforementioned activation is anambient service profile providing transaction services to the user. Insome embodiments, the service profile that is assigned to the deviceand/or network during the aforementioned activation is an ambientservice profile providing bill by account functionality for the network.In some embodiments, the service profile that is assigned to the deviceand/or network during the aforementioned activation is an ambientservice profile providing some amount of free networking or informationservice to entice the user to use the other ambient services. In someembodiments, the aforementioned ambient service is at least partiallyimplemented with device based service activity control or controlassistance. In some embodiments, the aforementioned ambient service isat least partially implemented by gateways, routers or switches in thenetwork that are programmed according to the ambient access profile forthe device to implement the ambient policies for network access control,routing control, traffic control or service monitoring and reporting forbill by account.

In some embodiments, activation is accomplished at least in part with atemporary service account in a manner that is automated and convenientfor the user or device owner. In some embodiments, at least some subsetof the temporary service account is replaced at a later point in time bypermanent service account subset in a manner that is also automated andconvenient for the user or device owner. In some embodiments, thetemporary service account settings (e.g., including the service profilesettings and/or the service plan settings) are pre-programmed into thedevice along with a temporary or permanent credentials set during themanufacturing or distribution process so that the device is activatedwith temporary credentials when it ships. In some embodiments, theaforementioned pre-programming for the network is performed via a secureset of server access equipment that networks into the network databasesused to define the service profile and/or the service plan. In someembodiments, the device is suspended once it is activated but before theuser is using it, and then resumed before or commensurate with the pointin time that the user begins to use it. In some embodiments, some subsetof the temporary service account is recycled once it is replaced, if thetemporary service account is not used after some period of time, if thetemporary service account is not upgraded to a permanent service accountafter some period of time, or if the activation is revoked from thedevice for some other reason. In some embodiments, more than one deviceis assigned to the same temporary service account. In some embodiments,a network accepts more than one device on the same temporary serviceaccount. In some embodiments, a device includes or is associated withtwo or more temporary service accounts, in which at least a subset ofthe temporary service account elements are different, so that if oneaccount is already being used to access the network then one or morereserve accounts can be drawn upon to gain access to the network. Insome embodiments, the temporary service account is associated with atemporary credentials set. In some embodiments, the temporary serviceaccount is associated with a permanent credentials set.

In some embodiments, un-activated devices are detected by the networkrouting equipment (e.g., service gateways or routers in hierarchicalnetworks or base stations with embedded gateways in flat networks) andthe device routing is programmed to re-direct un-activated devices to anactivation server network destination. For example, the activationserver can first inspect the information associated with the device todetermine if the device belongs to the list of devices, device types ordevice groups that the network is programmed to provide access to. Forexample, the information used to determine this can include device type,service provider, phone number, device ID, SIM ID or configuration,secure information used to qualify the device, IP address, MAC address,user, user group, VSP, OEM, device distributor, service distributor(master agent), service processor presence or configuration, presence orconfiguration of other software or hardware. There can also be someactivation definition information embedded in the credentials, orassociated with some portion of the credentials, or programmedadditionally on the device that informs the activation server as to theservice profile and/or service plan and/or service account that shouldbe established for the device. If activation information (the serviceprofile, service plan and/or service account information) is foundthrough association with the device credentials (e.g., device ID, phonenumber, IP address, MAC address, SIM or other security credentials)rather than being read directly from information embedded in the deviceor device credentials, then the pertinent aspects of the credentials canbe used as a cross reference to look up the service plan and/or serviceprofile information stored in a database networked to or within theactivation server. The activation information can include information todefine a wide variety of service plans and service profiles that whenproperly implemented on the network functions, and perhaps device ifnecessary, can provide for a wide range of service activity policies,service billing policies, transaction billing policies and serviceaccount types that can be associated with the device over the air orover the network.

In some embodiments, once the activation server has determined theactivation information from the device or from a look up based on someaspect of the device credentials, then the activation server initiatesthe necessary network settings and billing database entries to beprogrammed by sending the service profile instructions to the networkprovisioning and activation apparatus and the service plan instructionsto the billing system. In some embodiments, the activation server canthen also send the any necessary service profile and/or service plansettings required for the device to a provisioning and activationsupport software function on the device, such as various embodiments ofthe service processor, so that the device provisioning and activationcan be completed. The provisioning can be with permanent credentials ortemporary credentials, and the service account that is set up may bepermanent or temporary. In some embodiments, the activation processdescribed above is completed perhaps before the user has entered some orall of the user information necessary to set up a permanent serviceaccount, and, in these cases, a temporary service account can be set up.In some cases, the activation process can be completed in the backgroundbefore the user has completed an attempt to access the network and theservice profile can be set up to provide ambient services to a temporaryservice account. In some embodiments, the user is required to enter theinformation required to establish a permanent service account prior togaining full use of the device, either on the device, on a computer orin the store, so that by the time the user begins using the device theabove activation embodiments can provide for ambient services activationwith permanent account status so that the user can purchase a serviceupgrade or any transaction without entering any more accountinformation.

In some embodiments, a device status is changed from a temporary serviceaccount to a permanent service account. If the device is activated witha temporary service account, and the user information is available toset up a permanent account, then if the billing system rules andinterfaces allow for such, the user information can be changed from themock information to the actual user information while maintaining thesame account identifiers in the billing system. If the billing systemwill not allow for such, then the user information can be used toestablish a new account, the device credentials can be re-associatedwith the new account, in some cases, after modifying one or more of thedevice credential parameters, and the network functions can bere-programmed as required, and, in some cases, the device can bere-programmed as required to accommodate the new permanent account.

In some embodiments, code on the device pulls a temporary or permanentset of credentials. When the credentials are pulled, the networkassociates the device with an ambient service profile according to oneor more of the following: embedded device information identifying devicetype, service owner (e.g., VSP), user group, or user, or device ID iscross referenced to a database that is populated some time frommanufacturing time to post sale where the database provides informationidentifying device type, service owner (e.g., VSP), user group, or user.The device is then re-directed accordingly (e.g., for device based thisis a matter of setting the policies or loading the software for theservice processor, for the network based approach this is a matter ofpopulating the routing tables and service profile). For example,credentials can be re-cycled after a period of time, and/or some portionof the credentials can be redundant with other devices. For example,this is essentially a dynamic service for (temporarily) assigning devicecredentials, and the duration of the temporary credential validity forthat device ID can be time limited to give the user time to activate areal account or a free trial, session limited, or a longer duration oftime that is perhaps refreshed each time the device logs on. Forexample, the device could also already have permanent or temporarycredentials but not have a service account. The above process can beused to assign a temporary or permanent service account as well. Oncethe service account is assigned and the appropriate service profile ispropagated to the network elements, the device can then be directed toor use the appropriate activation profile service activities or theappropriate ambient service activities.

In some embodiments, the device is activated in the background in amanner that is virtually transparent to the user. For example, at somepoint in the distribution channel, the device is programmed to seek theactivation server system described above as soon as it is turned on, oras soon as some other event occurs like the user using the device or theuser attempting to gain access. When the pre-programmed event istriggered, the device connects to the network and the gateways orrouters re-direct the device to an activation server, as discussedabove. As also described herein, the activation server either derivesinformation from the device that informs the server what service thedevice should be activated with, or the server derives that informationfrom a database look up with a portion of the device credentials as thecross reference parameter. Once the activation server has determined theactivation information from the device or from a look up based on someaspect of the device credentials, then the activation server causes allthe necessary network settings and billing database entries to beconfigured/programmed by sending the service profile instructions to thenetwork provisioning and activation apparatus and the service planinstructions to the billing system. In some embodiments, the activationserver can then also send the any necessary service profile and/orservice plan settings required for the device to a provisioning andactivation support software function on the device, such as variousembodiments of the service processor, so that the device provisioningand activation can be completed. For example, the provisioning can bewith permanent credentials or temporary credentials, and the serviceaccount that is set up can be permanent or temporary.

In some embodiments, background activation is performed using theaforementioned activate/suspend process. At some point in thedistribution channel, the device is programmed to seek to resume serviceas soon as it is turned on, or as soon as some other event occurs likethe user using the device or the user attempting to gain access. Whenthe pre-programmed event is triggered, the device attempts to connect tothe network and the gateways or routers re-direct the device to anactivation server as described herein. As also described herein, theactivation server either derives information from the device thatinforms the server that the device is ready to resume service, or theserver derives that information from a database look up with a portionof the device credentials as the cross reference parameter. Once theserver is aware of this information, it sends a message to resumeservice to the billing system, or other network function that controlsthe suspend/resume function, and the service is resumed.

In some embodiments, background activation is performed as describedbelow. The service processor and the credentials are pre-programmedduring the manufacturing or distribution process to provide the desiredservice profile support and/or billing profile support for the desiredinitial ambient service. As described herein, this programming can beaccomplished with dedicated apparatus at the manufacturer ordistribution depot. Furthermore, the party responsible for defining theservice (e.g., typically the central provider, OEM, VSP, distributor ormaster agent) can network into the service processor programmingapparatus to control service processor and/or credential programming forall or a subset or group of the devices or device types locallyavailable. The service processor enabled device is programmed to seekthe activation server system described above as soon as it is turned on,or as soon as some other event occurs like the user using the device orthe user attempting to gain access. In some embodiments, the activationserver is the access control server previously discussed or the accesscontrol server can act in concert with another server that performs theactivation function. When the pre-programmed event is triggered, thedevice connects to the network and the gateways or routers re-direct thedevice to the activation server. As also described herein, theactivation server can communicate with the service processor to verifythe service processor security credentials, agents and configuration.

In some embodiments, if the activation server determines that thepre-programmed settings stored in the service processor need to bemodified to provide the latest version of the desired service, or if theservice processor agent software needs to be updated, then this can beaccomplished prior to completing the activation process. Once theservice processor configuration and settings are confirmed, theactivation server causes the necessary network settings and billingdatabase entries to be programmed by sending the service profileinstructions to the network provisioning and activation apparatus andthe service plan instructions to the billing system. Given that theservice processor can perform some or much of the service activitycontrol or control assistance, the service control options are generallylarger than without the service processor, and there can be lessconfiguration to perform for other networking equipment to complete theprovisioning and activation process. The provisioning can be withpermanent credentials or temporary credentials, and the service accountthat is set up can be permanent or temporary.

In some embodiments, pre-programming and pre-activation of devices withtemporary credentials and a temporary service account are used to shipdevices that are pre-activated. Given that the credentials are temporaryand can be recycled when the permanent credentials are assigned,concerns about using up too many pre-assigned credentials are reduced.In embodiments in which a portion of credentials elements can be usedfor multiple devices, this concern is further reduced. If there is aconcern about too many activated devices being assigned that are notactually active and generating service revenue, then the suspend/resumeprocess discussed herein can be employed. In some embodiments, thetemporary credentials and/or temporary account can be replaced withpermanent credentials and/or account assignments at any time as follows.When a pre-programmed event in the device is triggered, then the deviceinitiates a program that seeks the aforementioned activation server oranother server that has the capability of fulfilling the device requestto exchange the temporary credentials for permanent credentials and/orexchange the temporary account for a permanent account. The event thattriggers the credential exchange can be the same or different than theevent that triggers the service account exchange. The service accountexchange can typically be triggered by the point in time that the userenters account information.

In some embodiments, the aforementioned ambient service is partlyimplemented with a combination of the techniques for pre-provisioningduring manufacturing or distribution and at least partially implementingthe service activity control (e.g., access control, routing policy,traffic control, usage limits, and/or policy for useage limit overage)required for implementing ambient using the service policy provisioningcapabilities in the data path gateways, routers or switches in thenetwork. The gateways, router or switches are pre-programmed asdiscussed herein according to the ambient access profile for the deviceto implement the ambient policies for network access control, routingcontrol, traffic control or service monitoring and reporting for bill byaccount. In some embodiments, the provisioning credential elements arenot all pre-programmed before the device ships, but a subset of thecredential elements are programmed using the activation server techniquediscussed herein. This over the air automated provisioning is combinedwith the activation server reading the device credentials to derive theservice activity control settings for the gateways, routers or switchesthat will result in the desired ambient services activity controls.

In some embodiments, the aforementioned ambient service is implementedwith a combination of the techniques for pre-activation duringmanufacturing or distribution and at least partially implementing theservice activity control (e.g., access control, routing policy, trafficcontrol, usage limits, and/or policy for usage limit overage) requiredfor implementing ambient using the service policy control capabilitiesin the data path gateways, routers or switches in the network. Thegateways, router or switches are programmed to recognize thepre-activated device credentials as discussed herein according to theambient access profile for the device to implement the ambient policiesfor network access control, routing control, traffic control or servicemonitoring and reporting for bill by account. In some embodiments, thedevice activation profile and/or service account are not pre-programmedin the network and/or the device before the device ships but theactivation profile and/or service account are programmed using theactivation server technique discussed herein. This over the airautomated provisioning is combined with the activation server readingthe device credentials to derive the service profile activity controlsettings for the gateways, routers or switches that results in thedesired ambient services activity controls.

In some embodiment, a VSP capability is enabled by providing a securenetwork connection to the service policy settings tools that define thedevice pre-provisioning settings, the device pre-activation serviceprofile settings, the network equipment service activity control policysettings (e.g., access control, routing policy, traffic control, usagelimits, and/or policy for usage limit overage), and the network billingsystem database. By providing server tools that enable all thesesettings to be controlled (or perhaps only observed in the case of thebilling system) by a secure workstation or secure website interface thatnetworks into the equipment that programs the settings, and providingfor a secure partitioning of the devices that can be controlled by agiven secure workstation or secure website interface, a central providercan provide VSP services to multiple entities who all have differentdevice and service plan combinations that they desire different flavorsof ambient services for. These techniques can also be extended beyondambient to any device/service profile/service plan combo the VSP desiresto create. In some embodiments, the networking equipment is implementedto secure device service group domains in which the service policies fora group of devices can be controlled. In some embodiments, thepre-provisioning and pre-activation techniques are substituted with theover the air activation server techniques discussed herein, and a securedevice group partition capability is provided in the activation serveras well so that the activation server device group partition controlcapabilities can be added to the secure device group partition controlcapabilities of the network gateways, routers and/or switches, thedevice programming tools and the billing system to form a VSP partitionsolution for over the air activation of various device/service plancombinations. In some embodiments, the device groups are relativelysmall so that beta trials of arbitrarily large or small size can bedesigned and implemented by defining a service control group asdescribed above, and after fine tuning and perfecting the beta trialsettings the device group can be expanded to publish the automatedprovisioning and activation service settings to a larger user or devicegroup for production services.

In some embodiments, device based service activity control assistance(e.g., based on the various service processor embodiments describedherein) is combined with simplified provisioning techniques describedherein so that service processor enabled devices can be shipped withpre-provisioned credentials (temporary or permanent or can obtaincredentials in an automated manner that is convenient and efficient forthe user or device owner. In some embodiments, the service processorembodiments in combination with the manufacturing and supply chaincredentials and provisioning apparatus described elsewhere providevarious approaches for provisioning pre-provisioned service processorenabled devices. In some embodiments, the service processor embodimentsin combination with the activation server variants discussed aboveprovide various approaches for over the air or over the networksimplified post-sale provisioning for service processor enabled devices.For example, these embodiments can also be used for ambient servicesgiven that as discussed herein the service processor has capability toimplement service profile policies for deep control of ambient serviceactivity control.

In some embodiments, provisioning includes provisioning partial devicecredentials that include, for example, a secure certificate that is usedto authorize full credential provisioning and/or activation byperforming a process for a later look-up/validation of the full devicecredentials. For example, the look-up/validation of the full devicecredentials can be performed by a gateway, router or similar networkdevice that re-directs to a provisioning server and/or activation serveror other network components that either: (1) recognizes the partialcredentials that serve as a reference to direct the device communicationto a specific provisioning/activation server determined from the partialcredentials; or (2) does not recognize the partial credentials, anddirects the device communication to a less specificprovisioning/activation server that is not necessarily associated with areference to the partial credentials.

In some embodiments, if the partial device credentials (e.g., temporaryor permanent credentials) are being used for provisioning, then thepartial credentials are read (e.g., and/or other credentials can belooked up based on the partial credentials as described above). Thedevice is authorized if the proper credentials and/or secure certificateis present. The device credential provisioning is then completed (e.g.,using activation server commands or settings to a device based softwareand/or hardware element), and the credentials are, in some cases, alsocommunicated to the various network equipment elements.

In some embodiments, if the partial device credentials are being usedfor activation, then partial or full device credential provisioning isperformed, such as described above. A service account (e.g., temporaryor permanent service account) is created or looked up based on thepartial device credentials (e.g., a user account associated with thedevice through embedded partial or full credentials or a look upprocess, or based on a dynamically created/assigned temporary accountassociated with the device through embedded partial or fullcredentials). An initial service profile and, in some cases, an initialservice plan (e.g., service control policy settings including a billingprofile) are determined from embedded information and/or using a look upprocess (e.g., based on the device type and/or partial or full devicecredentials). The device is then programmed to enable access with theservice profile and plan, and, in some cases, the various networkcomponents/elements are programmed to enable the service profile andplan, and, in some cases, proper entries in the billing system are madeor confirmed, and the device credentials are, thus, activated forservice.

In some embodiments, the above described provisioning and/or activationprocesses are performed with the provisioning server(s) and/oractivation server(s) in the background with reduced, minimal or no userinput required, for example, after the device is sold to the user andthe user turns on the device so that by the time the user attempts toaccess the service using the device, the provisioning and/or activationprocess is already completed.

In some embodiments, device based service activity control assistance(e.g., based on the service processor embodiments) is combined withsimplified activation techniques described herein so that serviceprocessor enabled devices can be shipped with pre-activated accounts(temporary or permanent), or can obtain activated account status in anautomated manner that is convenient and efficient for the user or deviceowner. In some embodiments, the service processor embodiments incombination with the manufacturing and supply chain activation andprovisioning apparatus described elsewhere provide various approachesfor pre-activated service processor enabled devices. In someembodiments, the service processor embodiments in combination with theactivation server variants discussed above provide various approachesfor over the air or over the network simplified post-sale accountactivation for service processor enabled devices. These embodiments canalso be used for ambient services given that as discussed herein theservice processor has capability to implement service profile policiesfor deep control of ambient service activity control.

In some embodiments, the service processor can be combined with thepre-provisioning and pre-activation techniques described above to createan ambient service solution that will work on roaming networks in whichthe central provider or VSP has no control or minimal control over thenetwork elements. For example, the device includes a service processorpre-programmed for ambient service activity control as discussed herein,and the device credentials and other settings are pre-provisioned andpre-activated for the central provider network, all of which isdescribed in numerous embodiments disclosed herein. Provided that theservice provider has a roaming agreement with other service providers,or provided that the device may gain access to the roaming network, whenthe device is roaming it will be capable of ambient connectivity withbill by account functionality and all the other features of ambient.Furthermore, as also discussed herein, the ambient service activitycontrol policies can be different for different roaming networks toaccommodate the varying network costs and performance. Also, forexample, it would be permissible to sign up for initial services oradditional upgrade services with the central provider while roaming onthe roaming partner network. One of ordinary skill in the art willappreciate that this also allows for creating a VSP or MVNO for thepurpose of creating a clearing house for central provider serviceactivations according to geography or user choice. By using a globalmulti-mode modem module, and maintaining service agreements with amultitude of carriers, the MVNO or VSP can provide consistent ambientservices across multiple carriers and multiple geographies while stillmaintaining a good degree of cost control. Using bill by accountcapabilities, it is also possible to have an activation agreement wherea roaming service provider agrees to refined the cost of ambientroaming. From the ambient service platform, the VSP or MVNO can thenprovide service purchase options to the user based on the carriernetworks available to the device, or the VSP or MVNO can broker the useroff to any of the carriers by activating the device onto the carriersmain central provider service.

Accordingly, these embodiments provide flexible capabilities foractivating a device or group of devices with a broad range of serviceprofiles and service plans by simply programming the device with theproper credentials at some time during manufacturing or distribution, orsimply programming a database associated with the network so that aportion of the device credentials can be used to look up the desiredservice profile and service plan. For example, various activationembodiments described herein are highly convenient for the end user andneed not, in many cases, involve any human intervention.

The service processor 115, service controller 122, policy implementationand/or profile implementation and various embodiments disclosed hereinare applicable to conventional communication products as well as machineto machine applications. For example, if the machine to machine deviceincludes a service processor 115 with an activated account, then theservice profile settings can be optimized for machine communications toprovide only the limited access required to support the particularmachine to machine application. This allows for cost optimized accessservices and prevents the machine to machine device or access modem frombeing misappropriated and used for some other service access than thatintended. For example, by programming the machine to machinecommunications device at time of manufacture or during distribution withcredentials or partial credentials that provide for automatedprovisioning and activation as described herein, the device can beautomatically provisioned and activated on the service network with aservice account when deployed, thus eliminating the need for costly ortime consuming human intervention. The various embodiments that make itsimpler to design, manufacture, test and deploy devices may also beequally applied to machine to machine devices. These embodiments includethe service processor 115 developers kit and the automated provisioningand activation management tools among others. Also, the service analysisand test tools and the virtual service provider embodiments can also beapplied to machine to machine applications.

Verifiable Device Assisted Services for Intermediate Networking Devices

It should be appreciated that the various service monitoring,notification, control and billing embodiments disclosed herein can alsobe applied to intermediate networking device applications.

In some embodiments, an intermediate networking device is acommunications device in which the service processor 115 is configuredat least in part to allow the intermediate networking device to act as aservice intermediary or intermediate connection between the network andone or more end point devices (e.g., communications devices). Inaddition, a service controller 122 or other suitable network functionscan be employed to assist with the verifiable service usage monitoring,control and verification as disclosed in numerous embodiments describedherein. In some embodiments, an intermediate networking device does thisby implementing the service policies required for assisting serviceusage control of the intermediate networking device and connecting thenetwork to provide services to one or more end point devices that areconnected to the intermediate networking device. In some embodiments,the intermediate networking device also monitors the service useactivities of the intermediate networking device and/or the end pointdevices connected to the intermediate networking device. In someembodiments, the intermediate networking device and/or end point deviceservice usage is verified to ensure that the service usage is within theexpected ranges for the policies that are implemented. In someembodiments, the intermediate networking device connects with thenetwork using one modem technology and connects with the end pointdevices using one or more additional technologies. In some embodiments,an intermediate networking device connects the end point devices to thenetwork by passing, bridging, forwarding, routing, traffic shaping orotherwise allowing the end point devices to communicate with thenetwork. Example intermediate networking device embodiments include aWi-Fi to WWAN (e.g., 2G, 3G, 4G or other wireless wide area networkingaccess technology) bridge or router device, a Wi-Fi to DSL, cable orfiber gateway device, a WWAN to DSL or Cable femto cell device, a WWANand Wi-Fi to DSL, Cable or fiber back-hauled femto cell device, a WWANto WWAN router device, a WWAN to WLAN, WPAN or LAN bridge, router orgateway device, or a WWAN back up connection device for an enterpriserouter.

An intermediate networking device can also be provided in someembodiments by including a bridging, forwarding or routing functionbetween two modems in a communications enabled device that connects tothe network. For example, an intermediate networking deviceconfiguration can be a cell phone, smart phone, mobile internet deviceor any other mobile device that includes a WWAN modem and a Wi-Fi, WLAN,WPAN or LAN connection that can be used to connect to other end pointdevices. For example, the mobile device WWAN modem can connect to thenetwork, a service processor 115 can be included on the device processorto assist monitoring, controlling and billing for services between theWWAN network and end point devices connected to a Wi-Fi modem. Inaddition, a service controller 122 or other suitable network functionscan be employed to assist with verifiable service usage monitoring,control and verification as disclosed in numerous embodiments disclosedthroughout herein. In some embodiments, the Wi-Fi modem can beconfigured in access point mode or in ad hoc mode to communicate withother end point devices in the area covered by the mobile device WLANmodem. In this manner, a service processor 115 and a service controller122 or other suitable network functions can be employed to enable theverifiable service usage monitoring, control and verification asdisclosed in numerous embodiments described herein.

Another example embodiment is a notebook or sub-notebook computer with aWWAN modem and a Wi-Fi, Ethernet, Firewire, Bluetooth, near field orZigbee modem in which the notebook processor has a service processor 115running on the notebook processor and the service processor 115 is usedto assist monitoring, control and billing for services communicatedbetween the WWAN network and end point devices connected to the notebookor sub-notebook WLAN, LAN or WPAN. Another example embodiment is a Wi-Fihot spot with a service processor 115 capability. Another exampleembodiment is a WWAN back up modem in an access network router where theback up modem connection to the WWAN network is used when the main wirednetwork connection goes down, and a router processor or a WWAN back upmodem processor runs a service processor 115 to assist monitoring,controlling and billing for services between the WWAN network and theaccess router (e.g., the service provider may only wish to enable aconnection when the main wired network is down to ensure that the WWANmodem is not used for everyday access). In this manner, a serviceprocessor 115 and a service controller 122 or other suitable networkfunctions can be employed to enable the verifiable service usagemonitoring, control and verification as disclosed in numerousembodiments described herein.

Another example embodiment is a two-way home gateway configured toperform various functions such as reading power consumption of the homeand/or components in the home, providing WLAN, WPAN or LAN connectivityfor such components or to the power meters/controllers attached to suchcomponents, providing a WWAN or WAN connection to a network that reads,records, monitors and/or controls the home and/or component powerconsumption, and possibly to provide other wide area network servicesfor other devices in the home such as computers or entertainmentelectronics in a similar manner to the WWAN, DSL, cable and fibergateway embodiments. The WLAN, WPAN connections can be made with one ormore of Wi-Fi, Zigbee, Bluetooth, NFC or any other suitable wirelessmodem technology, and any desired wired LAN connections may be made withone or more of Ethernet, USB, Firewire, data over cable, data over powerline or any other suitable wired modem technology. The WWAN connectionscan be made with one or more of 2G (e.g. CDMA 1xRT, GPRS), 3G (e.g.WCDMA UMTS/HSPA/non-MIMO HSPA+, CDMA EVDOrA/B, 802.16d/e WiMax), 4G(e.g. LTE, MIMO HSPA+, MIMO 802.16m WiMax) or any other suitable modemtechnologies and the wired WAN connections may be made with one or moreof DSL, Cable, fiber or any other wired modem technology. A serviceprocessor 115 and a service controller 122 or other suitable networkfunctions can be employed to enable the verifiable service usagemonitoring, control and verification as disclosed in numerousembodiments disclosed throughout herein.

In some embodiments, an intermediate networking device can be used toconnect one end point device to a network and assist in implementingservice policies, or an intermediate networking device can connectmultiple end point devices to one or more networks and assist inimplementing service policies. In some embodiments, an intermediatenetworking device can be associated with one service profile, oneservice plan or one service account, or an intermediate networkingdevice can be associated with multiple service profiles, multipleservice plans or multiple service accounts. In some embodiments, endpoint devices connected to an intermediate networking device can haveservice usage policies implemented in aggregate for all end pointdevices, or service policies can be implemented differentially fordifferent end point devices.

In some embodiments, an intermediate networking device can have anetwork connection associated with a single account and manage QOSbetween end point devices under one umbrella service profile orcollection of profiles. In some embodiments, an intermediate networkingdevice can treat all connected end point devices equally from a servicesharing or QOS perspective so that, for example, service usage is basedon end point device demand and/or contention. In some embodiments, anintermediate networking device differentiates service QOS betweendifferent end point devices based on end point device service demand orservice usage patterns, EDP device type or device group, end pointdevice user or user group, end point device service account status orservice plan status, or end point device application type, and/ortraffic type or service type.

As discussed herein, the service processor 115 function assistingintermediate networking device implementation can be included on theintermediate networking device, can be included in part on theintermediate networking device and one or more end point devices, or canbe implemented mainly or entirely on one or more end point devices.

In some embodiments, an intermediate networking device can beconstructed in which end point devices connect to the intermediatenetworking device and gain access services to a WWAN network through aWWAN/Wi-Fi enabled intermediate networking device that is supplied withservices associated with a single account and service profile. Theintermediate networking device service processor 115 can assist inmonitoring, control and billing for WWAN service usage for all end pointdevices in the area covered by the intermediate networking device Wi-Filink. In some embodiments, end point devices receive service on firstcome first serve basis with no differentiation. In some embodiments, endpoint devices receive fair distribution of services so that if one endpoint device is using more significantly more service than the other endpoint devices, or is demanding more service than the intermediatenetworking device service profile settings provide for a single endpoint device (e.g., “bandwidth hogging”), then the high demand end pointdevice is throttled and the other end point devices are not. In someembodiments, end point devices receive hierarchical distribution ofservices based on one or more of service type, device type, user type,and/or account status. In some embodiments, an intermediate networkingdevice can provide for a large or unlimited number of end point devicesto connect to the network and simply control aggregate service usageparameters for the intermediate networking device WWAN connection. Insome embodiments, the intermediate networking device limits the numberof end point devices that are allowed to connect to the WWAN networkaccording the end point device count limits programmed in the serviceprocessor 115 service profile settings in the intermediate networkingdevice. In some embodiments, end point device traffic can be identifiedby various end point device credential aspects including, for example,by Wi-Fi ID, MAC ID, IP address, user ID, LAN tag, end point deviceagent credentials, and/or browser token or cookie. In some embodiments,the intermediate networking device service account can be billed foroverall service usage and/or by number of end point device connectionsallowed or experienced. In some embodiments, as the intermediatenetworking device user or owner signs up for a higher end point deviceconnection count, one ore more aspects of the service usage policyimplementation and/or profile implementations in the service processor115 profile settings can be increased.

The various verification techniques described herein can also be appliedto the intermediate networking device and extended to multiple end pointdevices. For example, network based service usage measures forverification can be applied to the intermediate networking device justas if the intermediate networking device were an end point device. Forexample, network based service usage measures (e.g., IPDR information)can be used to perform network verification checks to ensure thatintermediate networking device service usage is within acceptable rangesbased on intermediate networking device policy settings as similarlydescribed with respect to various device embodiments. In someembodiments, in the event intermediate networking device service usageis outside the policy limits set for the intermediate networking deviceservice processor 115, a notification can be sent to the intermediatenetworking device main account owner. The main intermediate networkingdevice account owner can also be required to acknowledge thenotification. The notification can also be sent to one or more otherusers of the intermediate networking device connection, includingpossibly all users. Other actions that can be taken if the network basedintermediate networking device service usage measure does not match thepolicy limits set on the service processor 115 include notify the user,notify the user and require acknowledgement, bill the user for serviceoverage, suspend the end point device, quarantine the end point device,SPAN the end point device, and/or alert network manager or alert anautomated network troubleshooting function. In some embodiments, adevice based usage measure can be verified against a network basedservice usage measure. It will now be apparent that the various serviceprocessor 115 verification embodiments, service controller 122verification embodiments, network verification embodiments,authentication embodiments, and tamper prevention or detectionembodiments, such as those shown in and described with respect to FIGS.22, 23, 26, 27 and 28, can be applied to intermediate networking deviceapplications and embodiments.

In some embodiments, it is desirable to match up individual end pointdevice or user intermediate networking device service usage with otherservice usage measures. For example, the individual end point deviceservice usage measures logged or reported from the end point devicesand/or the intermediate networking device can be aggregated to form atotal intermediate networking device usage measure that is compared toan aggregate intermediate networking device usage measure logged orreported in the network. In some embodiments, if these measures do notmatch, then an error condition results and an action is taken. In someembodiments, the aggregate intermediate networking device service usagemeasure is compared to the aggregate network based service usage measureand as long as these two measures are within an acceptable tolerance,then the intermediate networking device service usage measures aretrusted and can be used for deeper intermediate networking device andend point device usage measures for service control and/or billing thanmay be possible in the network. In such embodiments, the individual endpoint device service usage measures gained from the intermediatenetworking device or end point device can be used to verify end pointdevice service usage versus service policy allowances. In someembodiments, end point device service usage measures are compared withintermediate networking device measures for the same end point devices.

In some embodiments, the IPDR records for one or more networks caninclude individual end point device service usage information. This isthe case for example when the IPDRs include information broken down byend point device credential, such as IP address or other end pointdevice credential. In such cases, intermediate networking deviceembodiments can be employed in which the individual end point deviceservice usage information measured in the network can be compared withthe service usage policy allowances or limits for the end point device.Also, in some embodiments, the individual end point device service usagemeasures from an end point device service usage monitor and/or anintermediate networking device service usage monitor can be comparedwith the network based service usage information to verify an end pointdevice and/or an intermediate networking device service usage monitor isoperating properly.

As similarly described with respect to end point device embodiments withno intermediate networking device between the end point device and thenetwork, in some intermediate networking device embodiments, serviceusage and service usage monitor reports can be periodically verified byperforming a SPAN function on the traffic for an intermediate networkingdevice. The SPAN traffic can be analyzed in a real-time manner or in anon-real-time manner in the network and the results can be compared withthe intermediate networking device or end point device service policiesor service usage measures.

The synchronized device notification and acknowledgement embodiments canalso be employed in the case in which one service account is applied tothe intermediate networking device. The service usage counters in theintermediate networking device can be synchronized or updated with thenetwork based measures and the differences between the two may beminimized. The service usage notification can be sent to one or more ofthe end point devices connected to the intermediate networking device.For example, the notification can be sent to the intermediate networkingdevice manager or service owner, all end point devices or the mostactive end point devices.

Similarly, user preference feedback can be collected from one or more ofthe service users connected to the intermediate networking device. Insome embodiments, user preferences or user service selections or servicesettings are collected from one user or a subset of end point devicesused by the service subscriber. In some embodiments, more than oneservice user can provide preference information or service settings evenif there is only one user account. In some embodiments, there aremultiple service subscribers each providing preferences. In someembodiments, as similarly described with respect to various deviceembodiments, user preferences can be used set service control policiesthat provide the user with their selected balance of cost and servicecapability in a manner that meets network neutrality requirements.Similarly, in some embodiments, the service monitoring and customerresource management information collected on the intermediate networkingdevice or end point devices can be filtered according to user privacypreferences to maintain the level of user privacy selected by the user.

Adaptive intermediate networking device policy implementation can alsobe performed in the intermediate networking device service processor 115embodiments, as similarly described with respect to various deviceembodiments. In some embodiments, the service policy implementation forthe intermediate networking device can be adapted by the serviceprocessor 115 agents (e g., policy control agent 1692 working to controlthe settings in policy implementation agent 1690, and/or another serviceprocessor agent or function) to achieve a higher level service usagegoal. In some embodiments, the usage goals or adaptation can be based onaggregate end point device usage for the intermediate networking devicenetwork services, and in some embodiments, the higher level usage goalsor adaptation can apply to one or more individual end point devices.

In some embodiments, even though there is one intermediate networkingdevice account, there can be multiple options for multi-end point deviceor multi-user operation in which the number of end point devices, numberof users or service capabilities for some of the end point devices orusers are selectable. These parameters are accommodated by anintermediate networking device service profile that includes the servicecapabilities that are to be delivered to a multitude of end pointdevices or users. In some cases, some end point devices or users have adifferent profile within the intermediate networking device serviceprocessor 115 with differentiated capabilities as compared to theintermediate networking device service processor 115 profile for otherend point devices or users. This is the case for some of the examplesprovided herein. These multi-end point device or multi-user serviceprofiles in the intermediate networking device service processor 115 canshare services equally or can allow more capable access services to someend point devices or users than others. In some embodiments, a serviceprofile implemented by the intermediate networking device serviceprocessor 115 for one end point device or user is different than that inthe service profile implemented by the service processor 115 for anotherend point device or user (e.g., providing differentiated service profileimplementations by end point devices and/or users). End point devicescan be uniquely identified for purposes involving implementation ofdifferent service profiles in the intermediate networking device serviceprocessor 115 agents (e.g., depending on the embodiment, service monitoragent 1696, policy implementation agent 1690, policy control agent 1692,application interface agent 1693 and/or other service processor agentsor functions) based on a number of parameters, such as IP address, localarea network address (e.g., Wi-Fi address), MAC address end point deviceID, user ID, and/or end point device application layer tag. This allowsfor independent service usage monitoring and control for different endpoint devices or users.

In some embodiments, an intermediate networking device also bridgesservices to end point devices or users that have individually managedservice profiles, service plans or service accounts. As discussedherein, individual end point device service policy implementation and/orservice profile implementation can be accomplished by classifying endpoint device service usage according to an end point device identifierso that service monitoring, control assistance and reporting may bedifferentiated between one or more end point devices. These end pointdevice identifiers can then be associated with a different service planor account in the service processor 115 and/or billing system 123. Theend point device or user specific service usage monitoring, reporting,notification and control assistance can be accomplished by running oneor more profiles for each end point device or each user.

It will now be apparent that billing can also be implemented with asingle account encompassing service usage for all users or end pointdevices connected to an intermediate networking device, or forindividual users, end point devices, user groups or end point devicegroups connected to an intermediate networking device. As similarlydescribed with respect to the service profile, this is accomplished byassociating service usage events and associated billing events with aend point device identifier, user identifier, end point device groupidentifier, and/or user group identifier.

In some embodiments, end point devices or users connect to more than oneintermediate networking device with the same service account, serviceplan or service profile. In some embodiments, the intermediatenetworking device requires an authentication sequence for the end pointdevice or user before allowing connection to the network through theintermediate networking device. This authentication sequence can involvethe end point device communicating an active account or admissioncredential with the intermediate networking device. The intermediatenetworking device can compare the credential with a local database ormay query a database in the network to admit the end point device to theintermediate networking device network connection. In either case,provided the user credential or network authorization process is passed,the service processor 115 service profile settings for the end pointdevice are applied and service is then established as discussed herein.In these cases, the verification can be accomplished as describedherein. In some embodiments, even if the end point device does not havea service processor 115, provided that the intermediate networkingdevice service policy implementations and/or service profileimplementations are verified as described herein, then the intermediatenetworking device will accurately assist in control and reporting ofservice usage for the different end point devices or users, and theappropriate service policy controls and/or billing can be maintained.

In some embodiments, when the end point device attempts connection tothe intermediate networking device, if the user or end point device doesnot already have an active account or logon credential that theintermediate networking device recognizes, then the intermediatenetworking device can offer the end point device or user a service signup experience. This experience can be implemented in a number of ways,including a website, WAP site, portal, download of agent software, andother methods. For example, an automated recognition of new devices canredirect unauthorized end point devices to browse into a website, WAPsite, or portal site located on the intermediate networking device or inthe network. If the site is located on the intermediate networkingdevice, it can be cached and refreshed at a time of day when the networkis not overly busy. Once on the site, the user or end point deviceselects the plan choice they desire, inputs account information and, insome embodiments, downloads device agent software to aid in networkservice policy implementation and/or profile implementation with theintermediate networking device. Once the user signs up, the informationis logged into the network data base, the service account is establishedand the intermediate networking device service profile for that user orend point device is activated and the user can begin using the service.

In some embodiments, a website, WAP site, or portal site located in theintermediate networking device can be used to provide the end pointdevice user with a service usage monitor interface and a servicepurchase interface for cases in which the end point device does notposses any special software to allow it to display a more specializedservice usage monitor function for information received from theintermediate networking device or network service usage counters. Theservice usage monitor for the intermediate networking device can besynchronized, as similarly described with respect to various deviceembodiments. In some embodiments, the service usage notification systemcan also display cost data from a usage to cost look-up function. Insome embodiments, the service usage notification system can displayprojected service usage or projected cost, as similarly described withrespect to various device embodiments. The service usage monitor todrive these service notification embodiments can be located on one ormore of the end point device, the intermediate networking device or thenetwork.

In some embodiments, if multiple accounts are serviced by one or moreintermediate networking devices, verification can be performed on theservice controls for the end point device or user service usage. As willnow be apparent, just as with the intermediate networking device, theend point device or user service usage comparison with usage policysettings can be verified in the ways described herein. If the usage isfound to be out of policy, then any of the out of policy actionsdescribed herein can be performed, including, for example, notify theend user, notify and require acknowledgement, bill for overage, suspend,quarantine, SPAN, and/or flag to network manager or network errorhandling function. For example, the verification methods shown in anddescribed with respect to FIGS. 22, 23, 26, 27 and 28 can be applied forthe embodiments where intermediate networking devices have multipleaccount, multiple service plan, multiple service profile, multiple endpoint device, and/or multiple user capabilities.

It will be apparent that the various embodiments described herein forautomated provisioning and activation also can similarly be applied tothe intermediate networking device embodiments. It will also be apparentthat the various virtual service provider embodiments can similarly beapplied to the intermediate networking device embodiments.

Ambient services can be employed on the intermediate networking deviceand the ambient services can thus be provided to the end point devices.It will be apparent that the ambient service profile embodimentsdisclosed herein can similarly be applied to the intermediate networkingdevice, and then the intermediate networking device can supply thoseambient services to end point devices connected to the intermediatenetworking device. It will also be apparent that the intermediatenetworking device can provide an ambient service profile as describedherein to end point devices or users that have not yet signed up forservice, while providing other paid for service profiles to end pointdevices or users that have signed up for service.

Bill by account embodiments can similarly be applied to the intermediatenetworking device embodiments; For example, bill by account can be usedin embodiments in which all end point devices or users are connected tothe intermediate networking device under one account, or to embodimentsin which some end point devices or users are accounted for separatelywith different service accounts, service plans or service profiles. Ineither case, it will be apparent that using one or more of the end pointdevice or user identification credential aspects discussed herein can beused in a bill by account profile to account for any end point device orservice activity. In such embodiments, billing event reports for thoseactivities that include the end point device or user identifiers canalso be provided for billing mediation and reconciliation down to theindividual end point device or user level. For example, this allows forvery deep service monitoring and billing capabilities with intermediatenetworking devices.

The intermediate networking device embodiments described above also haveuses in machine to machine applications. It will be apparent that if theend point device includes the correct credentials to gain access to anexisting account, or to allow an automated provisioning and activationaccount to be established, then the end point device can be connected tothe network through the intermediate networking device without humanintervention. Furthermore, the service profile that is established withthe end point device for machine to machine communications can be set upto provide the access required to support the machine to machineapplication allowing for low cost access services and preventing the endpoint device from being misused for some service other than thatintended. For example, the verification techniques and embodimentsdisclosed herein can similarly be applied to such machine to machineapplications.

It will be apparent that the identifiers discussed above for bill byaccount mediation with accounting down to the individual end pointdevice or user level can be combined with a billing mediation server inthe network that accepts intermediate networking device billing eventswith end point device identification or user identification indexedbilling, performs the necessary bill by account mediation functions,formats the billing events into the format used by the billing system,and transmits the mediated billing information to the billing system123.

In some embodiments, the intermediate networking device serviceprocessor 115 functionality can be split. The division ranges from someor all of the service processor 115 on the device to some or all of theservice processor 115 on the intermediate networking device.

In some embodiments, all of the service processor 115 is on theintermediate networking device. The end point device does notparticipate in service processor 115 functions and has no serviceprocessor 115 interface software. In some embodiments, the end pointdevice has small subset of service processor 115 capabilities,including, for example, a service notification UI or a logon client withcredentials. In some embodiments, service monitoring is implemented onthe end point device or on both the end point device and in theintermediate networking device. In some embodiments, the end pointdevice has additional service processor 115 capabilities including, forexample, application layer tagging that associates application layeractivity with service processor 115 service monitoring or service policyimplementation and/or service profile implementation information. Thiscan be accomplished by a range of techniques, for example, transmittingthe application tagging information disclosed elsewhere to theintermediate networking device service processor 115 so that the policyimplementation may be accomplished with knowledge of the applicationlayer information. Another example involves assigning IP addresses inthe intermediate networking device networking stack to the end pointdevices so that different types of end point device traffic can berouted into service processor 115 traffic shaping queues, each queuehaving a policy profile implementation engine, and application layertagging information or similar traffic indentifying information is usedto determine which policy implementation engine the traffic should berouted to in order to accomplish the desired traffic shaping for thetraffic type, application type, service type, and/or content type. Insome embodiments, the traffic control policy is implemented on the endpoint device either with an application layer traffic controller, or byimplementing more of the service processor 115 functionality, assimilarly described with respect to various device embodiments. In theend point device service functionality example, most or all of theservice processor 115 functionality is implemented on the end pointdevice and the intermediate networking device functionality can bereduced to a bridging, forwarding or routing function between the endpoint devices and the network that performs little or no servicecontrol, monitoring and/or billing functions. For example, the serviceusage monitoring agents can also be provided on the end point device toaid in verification.

In embodiments in which the end point device requires agent software,the software can be loaded at time of manufacture or duringdistribution, loaded later, and/or made available for download throughthe intermediate networking device. In the case in which the end pointdevice agent SW is downloaded through the end point device, there can belocally cached copies of the SW for one or more OS variants stored in acache on the intermediate networking device, with the cache beingupdated over the network at convenient or conducive times, or thesoftware can be downloaded live over the network when it is needed bythe end point device. Logging the service usage to download thissoftware is another example in which bill by account functionality canbe used to track network traffic that may not be desirable to bill to aend point device owner or user, and bill by account functionality can beused to log and mediate such usage out of the user or end point deviceowner's bill.

Any end point device agent software required to connect to theintermediate networking device can also be implemented as a serviceprocessor 115 developer's kit as described herein and distributed to aidmanufacturers, service provider and virtual service providers inbringing new devices onto networks with intermediate networking devicecapability.

In the case of a femto cell intermediate networking device, in someembodiments, it is desirable to facilitate handover from the WWANnetwork to the femto cell. In some embodiments, this provided in theintermediate networking device service processor 115 in a variety ofways. In some embodiments, the voice and data traffic is routed througha VPN tunnel controlled by the service processor 115 and connected to anetwork element, such as the transport gateway or another specifiedtraffic concentration destination for the femto cell. In someembodiments, the voice traffic, the data traffic or both can be routedin secure or open Internet channels to different destinations, or thedata can be routed directly to the Internet destination specified by thepackets. In some embodiments, the femto cell intermediate networkingdevice controls the femto cell frequencies or local frequency channelstrength surveys over the intermediate networking device controlchannel. In some embodiments, the service processor 115 has a VPNconnection to a network base station hand off controller to assist inhandoff to and from the WWAN network and/or has the capability toinstruct the end point device and the base station handoff controller.In some embodiment, whenever an end point device authenticated for femtocell access is within range of the femto cell, the service providerdesires to set up a service processor 115 profile to get the end pointdevice to connect to the femto cell even if it has a strong signal withone or more WWAN base stations so that the WWAN traffic may beoffloaded. In some embodiments, the service processor 115 can form asecure control plane link with network AAA functions to manageauthorization and admission of end point devices the femto cell has notyet admitted, or the network policies can require re-authorization everytime a end point device attempts access. Once an end point device isconnected to the femto cell intermediate networking device, theverifiable traffic monitoring, control and billing functions describedherein can be applied to various application embodiments. For example,the intermediate networking device service policy verificationtechniques disclosed herein, as similarly described with respect tovarious device embodiments, can similarly be applied to the femto cellintermediate networking device embodiments.

In some embodiments, the service provider desires to keep the number ofend point devices or users that access an intermediate networking devicebelow a certain count specified in the service processor 115 profile. Insome embodiments, this is accomplished by controlling the number of IPaddresses allowed onto the intermediate networking device local areaside connection. In some embodiments, this is facilitated by observingthe end point device identification parameters available in the endpoint device traffic. In some embodiments, this is facilitated byobserving the traffic patterns to determine the likely number of devicesconnecting to the network. For example, traffic demand patterns can beexamined to determine how many users are likely to be demanding accessat one time. Although the foregoing embodiments have been described insome detail for purposes of clarity of understanding, the invention isnot limited to the details provided. There are many alternative ways ofimplementing the invention. The disclosed embodiments are illustrativeand not restrictive.

1. A system, comprising: a processor of an intermediate networking device configured to: provide a service intermediary or intermediate connection between a first network and one or more communications devices; implement a first service profile set for assisting control of the intermediate networking device use of a first service set on the first network, wherein the first service profile set includes one or more service profiles, each profile being associated with either the intermediate networking device or a communications device, each profile including a plurality of service policy settings; monitor use of the first service set based on the first service profile set; and a memory of the intermediate networking device coupled to the processor and configured to provide the processor with instructions, wherein the implementation of the first service profile set is verified.
 2. The system recited in claim 1, wherein the one or more communications device include one or more mobile communications devices, and the first network service includes one or more Internet based services.
 3. The system recited in claim 1, wherein the one or more communications device include one or more of the following: a mobile phone, a PDA, an eBook reader, a music device, an entertainment/gaming device, a computer, laptop, a netbook, a home networking system, and a modem or communications device supporting machine to machine communications.
 4. The system recited in claim 1, wherein the intermediate networking device communicates, forwards, routes, passes or bridges network communications between the first network and one or more of the communications devices.
 5. The system recited in claim 1, wherein the intermediate networking device includes a first modem to connect with the first network and a second modem to connect with the one or more communications devices.
 6. The system recited in claim 1, wherein the intermediate networking device includes a first modem to connect with the first network and a second modem to connect with the one or more communications devices, and wherein the first modem communicates using one or more of the following communication protocols: WiFi, WWAN, Bluetooth, Ziggby, satellite, DSL, and DOCSIS/cable.
 7. The system recited in claim 1, wherein the intermediate networking device includes a first modem to connect with the first network and a second modem to connect with the one or more communications devices, and wherein the second modem communicates using one or more of the following communication protocols: WiFi, WWAN, Bluetooth, Ziggby, satellite, DSL, and DOCSIS/cable.
 8. The system recited in claim 1, wherein the intermediate networking device includes one or more of the following: a WWAN to WiFi bridge or router, a femto cell, a wired WAN access router or gateway, a DSL modem, a cable modem router, a gateway, a satellite modem router or gateway, a cell phone, a handheld device, and a computer.
 9. The system recited in claim 1, wherein a first service processor is located on a first communications device in communication with the intermediate networking device, and wherein the service processor implements the first service profile set for assisting control of the intermediate networking device use of the first service set on the first network.
 10. The system recited in claim 1, wherein a first portion of a first service processor is located on a first communications device in communication with the intermediate networking device, and a second portion of the first service processor is located on the intermediate networking device, and wherein the service processor implements the first service profile set for assisting control of the intermediate networking device use of the first service set on the first network.
 11. The system recited in claim 1, wherein a first portion of a first service processor is located on a first communications device in communication with the intermediate networking device for service usage monitoring or service usage notification assistance or billing assistance, and a second portion of the first service processor is located on the intermediate networking device, and wherein the service processor implements the first service profile set for assisting control of the intermediate networking device use of the first service set on the first network.
 12. The system recited in claim 1, wherein a first service processor is located on a first communications device in communication with the intermediate networking device, and a second service processor is located on the intermediate networking device, and wherein the first service processor implements the first service profile set for assisting control of the intermediate networking device use of the first service set on the first network, and the second service processor implements a second service profile set for assisting control of the intermediate networking device use of the first service set on the first network.
 13. The system recited in claim 1, wherein the processor of the intermediate networking device is further configured to: verify the implementation of the first service profile set using a first service processor located on a first communications device.
 14. The system recited in claim 1, wherein the processor of the intermediate networking device is further configured to: verify the implementation of the first service profile set using a first service processor located on a first communications device if more than one user or communications device is communicating with the intermediate networking device.
 15. The system recited in claim 1, wherein the processor of the intermediate networking device is further configured to: verify the implementation of the first service profile using a first service processor located on a first communications device; and verify an implementation of a second service profile set using a second service processor located on a second communications device.
 16. The system recited in claim 1, wherein the processor of the intermediate networking device is further configured to: collect first service set usage information from a first service processor executed on a first communications device to assist the monitored use of the first service set.
 17. The system recited in claim 1, wherein the processor of the intermediate networking device is further configured to: collect first service set usage information from a first service processor executed on a first communications device to assist the monitored use of the first service set if more than one user or communications device is communicating with the intermediate networking device.
 18. A method, comprising: providing a service intermediary or intermediate connection between a first network and one or more communications devices; implementing a first service profile set for assisting control of the intermediate networking device use of a first service set on the first network, wherein the first service profile set includes one or more service profiles, each profile being associated with either the intermediate networking device or a communications device, each profile including a plurality of service policy settings; and monitoring use of the first service set based on the first service profile set, wherein the implementation of the first service profile set is verified.
 19. A computer program product, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for: providing a service intermediary or intermediate connection between a first network and one or more communications devices; implementing a first service profile set for assisting control of the intermediate networking device use of a first service set on the first network, wherein the first service profile set includes one or more service profiles, each profile being associated with either the intermediate networking device or a communications device, each profile including a plurality of service policy settings; and monitoring use of the first service set based on the first service profile set, wherein the implementation of the first service profile set is verified. 